slachiewicz commented on PR #1361:
URL:
https://github.com/apache/maven-assembly-plugin/pull/1361#issuecomment-5396170734
Closing: 1.3.0 is broken, not this plugin.
`org.codehaus.plexus.build.progress.DefaultProgress` in 1.3.0 carries both
`@Singleton` and
`@MojoExecutionScoped`, and 1.3.0 newly lists it in
`META-INF/sisu/javax.inject.Named`. Guice rejects two
scope annotations on one class, so the injector for the plugin realm fails
to build and no mojo can be
loaded from it.
The failure surfaces as `Unable to load the mojo ...
java.util.NoSuchElementException`, which is the
symptom rather than the cause. The cause is logged as a warning while the
realm is built:
```
com.google.inject.CreationException: Unable to create injector, see the
following errors:
1) [Guice/DuplicateScopeAnnotations]: More than one scope annotation was
found: Singleton and MojoExecutionScoped.
\_ installed by: WireModule -> PlexusBindingModule
```
That is the whole reason 288 of the 290 integration tests fail here while
`master` is green. Nothing in
this repository needs changing.
Tracked upstream as
[codehaus-plexus/plexus-build-api#127](https://github.com/codehaus-plexus/plexus-build-api/issues/127),
with a verified fix: drop `@Singleton`. The 1.3.0 release notes now carry
the warning. Reopen the bump
once 1.3.1 is out.
*This comment was created with AI assistance.*
--
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]
