Seems like there's no positive reception to those issues for now, which is sad. All those classes moving from Java SE to Java EE to Jakarta EE have created real dependency hell.
wt., 12 lis 2019, 17:34 użytkownik David Karlsen <[email protected]> napisał: > Also see https://issues.apache.org/jira/browse/CXF-8117 > IMO far too many obsolete deps are added (at least the more edge-cases > could be softened with optional/provided). > Also using the standard artifacts http://repo1.maven.org/maven2/javax > (now: > http://repo1.maven.org/maven2/jakarta/) makes sense. > Here is an issue for boot/spring: > https://github.com/spring-projects/spring-boot/issues/16111 on the > subject. > > tir. 12. nov. 2019 kl. 16:52 skrev morvael <[email protected]>: > > > My project uses > > > org.jboss.spec.javax.transaction:jboss-transaction-api_1.3_spec:2.0.0.Final > > I also use duplicate finder Maven plugin to avoid multiple classes with > the > > same name on classpath. I have a conflict with > > org.apache.geronimo.specs:geronimo-jta_1.1_spec:1.1.1 pulled in by CXF. > It > > is safe to exclude that CXF dependency if I only use CXF's JAX-WS with > http > > transport and JAX-RS? Why is CXF pulling so much obsolete libraries? > > > > Regards, > > Dominik > > > > > -- > -- > David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen >
