Ok, sorry I didn't mention before you released, I wasn't sure of my setup. https://issues.apache.org/jira/browse/MNG-7214
Delany On Sat, 14 Aug 2021 at 20:56, Michael Osipov <micha...@apache.org> wrote: > Thank you very, very much for this edge case. > > Gosh, I hate all of this JBoss conglomerate with a passion. > > This is our problem: > > [INFO] | +- org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.3.4:compile > > [INFO] | | \- javax.enterprise:cdi-api:jar:1.0:compile > > [INFO] | | \- javax.annotation:jsr250-api:jar:1.0:compile > > Guess what, although javax.enterprise:cdi-api is in javax namespace its > parent is > > <parent> > > <groupId>org.jboss.weld</groupId> > > <artifactId>weld-api-parent</artifactId> > > <version>1.0</version> > > <relativePath>../parent/pom.xml</relativePath> > > </parent> > > WTF? How is this possible? Who signed this? The API should be completely > decoupled of Weld. The repo is burried in the parents. This is > absolutely unacceptable. It leaks now in the entire buildchain for > everyone who depends on our artifacts. > > We can do two things here: > 1. Exclude this transitive dependency and lose @Typed in Plexus to JSR > 330 migration > 2. Ask Stuart McCulloch to push a new Sisu release with updates to CDI > 1.2 which parents do not have a repo anymore. > > Still leaves a very bad after taste.... > > Please file an issue, I will try talk to Stuart. > > I think this is ugly enough to justify 3.8.3 for all of those who > depends on our JARs. Plain Maven users aren't affected. > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
