Closed jukzi closed 6 months ago
I could need some help here: why does the maven command [1] works with jdt.core [2] but fails with jdt.ui or jdt.debug?
Could not find artifact org.eclipse:eclipse-platform-parent:pom:4.31.0-SNAPSHOT
@akurtakov any idea ?
[1] https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blame/9dd978a9529696cef1ba1eb1700c24ff273d2dab/.github/workflows/codeQLworkflow.yml#L82
mvn --batch-mode -V -U -ntp -Dcompare-version-with-baselines.skip=true -Pbree-libs -DskipTests=true --fail-at-end clean verify
[2] https://github.com/eclipse-jdt/eclipse.jdt.core/actions/runs/7887538988/job/21523009449?pr=2013
Most likely due to the fact that jdt.core passes -Pbuild-individual-bundles to the maven invocation via https://github.com/eclipse-jdt/eclipse.jdt.core/blob/master/.mvn/maven.config but jdt.debug doesn't.
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.