[MNG-8168] Core release 3.9.8 has impact to the invoker plugin.
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Ozgun OZ](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ozgun)** opened **[MNG-8168](https://issues.apache.org/jira/browse/MNG-8168?redirect=false)** and commented
The integration tests of my [extension](https://github.com/HomeOfTheWizard/spring-bridge-maven-extension) do not work if I upgrade the maven-core dependency from 3.9.7 to 3.9.8.
The release seems to have an impact on the invoker plugin.
It does not see the extensions.xml in the .mvn directory of my IT tests.
When I run the project in the IT folder myself, all works good, but when run with the invoker:run, the extension is not picked up.
{**}Might help{**}: the extension uses a custom Guice module and according to the release note, 3.9.8 includes a new release of [SISU](https://maven.apache.org/docs/3.9.8/release-notes.html)
---
**Affects:** 3.9.8
Contributor guide
Research direction
Start by reproducing the integration test with maven-core 3.9.8 and invoker:run, comparing extension discovery in .mvn/extensions.xml against version 3.9.7. Investigate the custom Guice module and SISU change mentioned in the report; done means the extension is picked up when the test runs through invoker:run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100