Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
Description
The org.jdom module is jboss.api=unsupported in EAP and is not actually used by WF or added as a dependency by it to deployments. It looks like it probably should have been made private way back in 2012 when it was made 'unsupported' in EAP. The 'unsupported' is inappropriate in WF so it got removed, resulting in it becoming 'public'.
The only module that depends on org.jdom is org.jaxen. Jaxen's pom declares it as an optional dependency. Here is the production code use of jdom by jaxen:
src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Attribute; src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.CDATA; src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Comment; src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Document; src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Element; src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Namespace; src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.ProcessingInstruction; src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Text; src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.input.SAXBuilder; src/java/main/org/jaxen/jdom/XPathNamespace.java:import org.jdom.Element; src/java/main/org/jaxen/jdom/XPathNamespace.java:import org.jdom.Namespace;
DocumentNavigator is nowhere used by WF or its libraries. XPathNamespace is only used by DocumentNavigator. So, our uses of jaxen don't require jdom. That dependency should be optional so galleon can skip provisioning it in optimized installations.
