Hi folks, There are 2 Eclipse JAXB related projects[1] that produce 10 artifacts with 3 groupIds that are spread over 5 JBoss modules: Project groupId artifactId JBoss module dependencies eclipse-ee4j/jaxb-ri <https://github.com/eclipse-ee4j/jaxb-ri> org.glassfish.jaxb jaxb-runtime com.sun.xml.bind - com.github.relaxng - com.sun.istack - com.sun.xml.txw2 - com.sun.xsom - javax.api - javax.xml.bind.api - javax.xml.stream.api jaxb-xjc jaxb-jxc codemodel txw2 com.sun.xml.txw2 - javax.api xsom com.sun.xsom - com.github.relaxng - javax.api com.sun.xml.bind.external rngom com.sun.xml.bind See above relaxng-datatype com.github.relaxng N/A eclipse-ee4j/jaxb-istack-commons <https://github.com/eclipse-ee4j/jaxb-istack-commons> com.sun.istack istack-commons-runtime com.sun.istack - javax.activation.api - javax.api istack-commons-tools All these JBoss modules are private and do not depend on other modules except *com.sun.xml.bind*, we want to know if it is possible to simplify it by living with only 1 JBoss module: com.sun.xml.bind[2]. So if any projects that are built based on WildFly depend on the following 4 JBoss modules, please comment if it is OK to do the merge(by updating your dependencies to com.sun.xml.bind instead): com.github.relaxng com.sun.istack com.sun.xml.txw2 com.sun.xsom Thank you :) [1] https://github.com/eclipse-ee4j/jaxb-ri https://github.com/eclipse-ee4j/jaxb-istack-commons [2] https://issues.redhat.com/browse/WFLY-12913 Best Regards -- Lin Gao Senior Software Engineer JBoss Sustaining Engineering Team