gnodet opened a new pull request, #26838: URL: https://github.com/apache/camel/pull/26838
## Summary The Dependency Analysis workflow was failing intermittently with: ``` [ERROR] Failed to execute goal eu.maveniverse.maven.plugins:pilot-plugin:0.4.0:dependencies on project camel-management: Failed to analyze dependencies: The following artifacts could not be resolved: org.apache.camel:camel-core:test-jar:4.23.0-SNAPSHOT (absent): Could not find artifact org.apache.camel:camel-core:test-jar:4.23.0-SNAPSHOT ``` ## Root cause `pilot:dependencies` 0.4.0 resolves **all** declared dependency artifacts (including test-scope) before running its analysis — even when `-Dpilot.skipTestScope=true` is set. The flag skips test-scope *analysis*, not test-scope *resolution*. `camel-management`, `camel-main`, and several components declare `camel-core:test-jar` (classifier=`tests`) as a test-scope dependency. The test-jar is only produced at the `package` phase, so it is never present in a clean CI checkout. This causes the failure. ## Fix Install an empty stub JAR with classifier=`tests` before the compile step, using the same pattern already in place for other unresolvable SNAPSHOT artifacts (`camel-spring-xml`, `camel-test-spring-junit6`, etc.). The stub satisfies pilot's resolution step. Its contents are irrelevant because test-scope analysis is skipped entirely by `-Dpilot.skipTestScope=true`. Also corrects a comment that incorrectly stated `pilot.skipTestScope=true` prevents artifact resolution — it only skips analysis. ## Testing The failure was confirmed from the `dep-check-output.txt` artifact of a recent workflow run (run ID 35979984649). The fix follows the established pattern that has successfully addressed the same root cause for other SNAPSHOT build artifacts. Fixes: https://issues.apache.org/jira/browse/CAMEL-24985 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
