gnodet opened a new pull request, #461:
URL: https://github.com/apache/maven-integration-testing/pull/461

   ## Problem
   
   When Maven loads `maven-it-plugin-project-interpolation:2.1-SNAPSHOT` during 
a forked IT execution, it needs to resolve the plugin's transitive 
dependencies. The plugin depends on `maven-it-helper`, which declares 
`org.junit.jupiter:junit-jupiter:5.8.0` as a compile-scope dependency.
   
   The IT suite configures a `settings.xml` that redirects `central` to 
`file:target/null` to enforce that all required artifacts come from the 
pre-populated `it-local-repo`. However `junit-jupiter:5.8.0` is not installed 
into `it-local-repo` by the outer build (it is downloaded as a build-time dep, 
not installed as a plugin runtime dep), so the forked Maven fails with:
   
   ```
   Could not find artifact org.junit.jupiter:junit-jupiter:jar:5.8.0
   in central (file:target/null)
   ```
   
   ## Fix
   
   Add `org.junit.jupiter:junit-jupiter` to the exclusion list on the 
`maven-it-helper` dependency in the plugin POM. The other test-only deps 
(`maven-artifact`, `maven-verifier`, `junit:junit`) were already excluded; this 
adds the matching JUnit 5 exclusion.
   
   The plugin code itself does not import or use `junit-jupiter` at all — the 
dep on `maven-it-helper` exists solely to exercise Maven's `${project.version}` 
interpolation in a plugin's dependency section.


-- 
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]

Reply via email to