1:35 p.m.
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
1:37 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-3666) Replace the dom4j dependency with a jarjar'ed equivalent
[ http://jira.jboss.com/jira/browse/JBAS-3666?page=comments#action_12343494 ]
Dimitris Andreadis commented on JBAS-3666:
------------------------------------------
Scott put the jarjard dom4j jar into the repository here:
http://repository.jboss.com/dom4j/1.6.1.jarjar
It contains the dom4j-jarjar.jar (which uses an org.jboss.dom4j root package namespace),
and the jarjar build script.
All that is left is to update all the bootstrap modules which use
dom4j(jmx/j2se/system/system-jmx) to use the new namespace. The dom4j jars could be
embedded into one of these module output jars as an implementation detail to reduce the
number of bootstrap jars if desired.
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
9 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-3666) Replace the dom4j dependency with a jarjar'ed equivalent
[ http://jira.jboss.com/jira/browse/JBAS-3666?page=all ]
Dimitris Andreadis closed JBAS-3666.
------------------------------------
Resolution: Done
Assignee: Dimitris Andreadis
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
Assigned To: 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
9 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-3666) Replace the dom4j dependency with a jarjar'ed equivalent
[ 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
12:44 p.m.
New subject: [JBoss JIRA] Reopened: (JBAS-3666) Replace the dom4j dependency with a jarjar'ed equivalent
[ http://jira.jboss.com/jira/browse/JBAS-3666?page=all ]
Scott M Stark reopened JBAS-3666:
---------------------------------
Assignee: Scott M Stark (was: Dimitris Andreadis)
The current 4.0 build is failing with errors like:
2006-09-21 10:25:42,343 WARN [org.jboss.system.ServiceController] Problem starting
service jboss.web.deployment:war=invoker.war,id=1836912571
java.lang.NoClassDefFoundError: org/dom4j/DocumentException
at
org.jboss.security.jacc.JBossPolicyConfigurationFactory.<init>(JBossPolicyConfigurationFactory.java:57)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at
javax.security.jacc.PolicyConfigurationFactory.getPolicyConfigurationFactory(PolicyConfigurationFactory.java:91)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:351)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
This particular case is due to the jboss/common snapshot-Branch_1_0 still having dom4j
dependencies? I'm looking into it.
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
Assigned To: Scott M Stark
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
1:12 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-3666) Replace the dom4j dependency with a jarjar'ed equivalent
[ http://jira.jboss.com/jira/browse/JBAS-3666?page=all ]
Scott M Stark closed JBAS-3666.
-------------------------------
Resolution: Done
The problem was the reuse of a snapshot release in the build resulting in the local build
repository not being in synch with the version described by this issue. Snapshots are
evil.
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
Assigned To: Scott M Stark
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
7243
days inactive
7246
days old
5 comments
2 participants
participants (2)
-
Dimitris Andreadis (JIRA) -
Scott M Stark (JIRA)