slachiewicz commented on PR #376:
URL: https://github.com/apache/maven-filtering/pull/376#issuecomment-5401670515
Closing: `plexus-build-api` 1.3.0 should not be adopted. Two regressions in
that release make it unusable, and this build hit the first of them.
- codehaus-plexus/plexus-build-api#127 — `DefaultProgress` 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 fails for any realm holding the jar.
- codehaus-plexus/plexus-build-api#125 — `DefaultBuildContext` gained a
`LegacySupport` constructor dependency and can no longer be provisioned outside
a Maven session.
What that looked like here, on `ubuntu-latest jdk-17-zulu` with Maven
3.10.0-rc-1:
```
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.
at ClassRealm[plexus.core, parent: null]
```
`EscapeStringTest` 1 error, `DefaultMavenResourcesFilteringTest` 25 errors —
the whole module.
Worth recording that this was the bump and not the environment: sibling
Dependabot PRs #377 and #378 opened against the same branch minutes apart, and
#378 passes the identical `ubuntu-latest jdk-17-zulu 3.10.0-rc-1` cell that
this one fails. Same base, same runner image, same hour.
Reopen or supersede this once a fixed release is out. Details from this
occurrence are on codehaus-plexus/plexus-build-api#127.
*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]
