Hi everyone, CXF dependency management is based on being self contained. Was not working bad years ago when it was using geronimo bundles but since some years it becomes more and more work to integrate each cxf release because dependencies became greedy.
Here are the main challenges: 1. spec jars are using jakarta (whereas the app/soft can use javax, geronimo, smix and other flavors) 2. most modules leak not required dependencies (thinking to jta, jms, rmi out of my head) 3. some java 11 oriented dependencies are popping up whereas they are not needed in 80% of the cases (activation, jaxb for ex) 4. module rarely/never mark not required dependencies as being optional/provided To give you an idea, it is not uncommon to have ~15 exclusions to all cxf modules when importing them. Is it something identified? Any plan to enhance this (like having aggregator poms "cxf-spec", "cxf-dep-optional", "cxf-java9" to ease the exclusions? making it provided and having aggregator pom with the depencencies marked as required (strict module vs consumed pom modules))? Side note: explosing cxf-core can also help, it contains a lot of optional stuff which can also make this work harder to maintain. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance>
