Feature: Reduce number of jars

[mattrpav]

Currently, an application using JAXB needs a ton of jars. It would be ideal if it was reduced down to:

1. Jakarta API spec jar
2. One implementation jar

I believe the current breakout was done to provide for the migration of JAXB out of the JDK and to support javax to jakarta migration. With the Jakarta migration mostly behind us as a Java community, it would be great to reduce the dependency noise when using JAXB.

[lukasj]

Which jar(s) listed in the docs you are proposing for removal?

Note that XJC can be run with jaxb-core.jar, jaxb-impl.jar, jaxb-xjc.jar or jaxb-core.jar, org.eclipse.persistence.moxy, jaxb-xjc.jar jars on the path

[mattrpav]

I'm proposing reducing the transitive dependencies-- org.glassfish.jaxb/txw2, com.sun.istack/istack-commons-runtime, fastinfoset, stax-ex.

[lukasj]

How do you propose to do it? There exist other consumers of these small libraries outside of jaxb itself, their maintenance cost is close to zero and disturbance any change here can cause in the overall ecosystem is hard to evaluate. Think of them as linux utilities - they do one thing and do it right, all together form the swiss-knife which common end user typically uses.

I believe the current breakout was done to provide for the migration of JAXB out of the JDK and to support javax to jakarta migration.

No. Some of these projects were done this way around the end of the previous/beginning of current century and jaxb itself was just built on top of them. Btw hudson, now a days also jenkins, was primarily created to build all these (in)dependent projects in one go and that process is what we know these days as CI/CD (but here we are talking about year ~2005)

[lukasj]

See https://github.com/eclipse-ee4j/metro-wsit/blob/master/etc/metro-dependencies.md