[jboss-jira] [JBoss JIRA] Commented: (JBAS-3666) Replace the dom4j dependency with a jarjar'ed equivalent

Thu Sep 21 10:00:01 EDT 2006

    [ http://jira.jboss.com/jira/browse/JBAS-3666?page=comments#action_12343744 ] 

Dimitris Andreadis commented on JBAS-3666:
------------------------------------------

So the standalone common module does not depend on dom4j anymore. This is currently accessed through snapshot-Branch_1_0, and will be part of jboss-common-1.0.0.GA

The jmx module now uses the jarjar org.jboss.dom4j version of dom4j, bundled in jboss-jmx.jar. The old dom4j lib is removed from JBOSS_HOME/lib.

The latest dom4j.jar lib is copied in JBOSS_HOME/server/all|default/lib, so modules like 'deployment' and 'console' that have minor dependencies on it can use it, plus user code that depended on dom4j will still work.

Updating dom4j / jaxen should now be easily done, if necessary.

> Replace the dom4j dependency with a jarjar'ed equivalent
> --------------------------------------------------------
>
>                 Key: JBAS-3666
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3666
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Dimitris Andreadis
>             Fix For: JBossAS-4.0.5.GA
>
>
> Ofuscate the dom4j classes using jarjar  to avoid these leaking into the user space. The dom4j subset we included in 4.0.4 broke use of xpath from dom4j since it has an explicit dependency on jaxen.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira