You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Lukas Theussl (JIRA)" <co...@jakarta.apache.org> on 2006/01/02 22:33:00 UTC
[jira] Created: (JELLY-226) Upgrade dom4j and jaxen
Upgrade dom4j and jaxen
-----------------------
Key: JELLY-226
URL: http://issues.apache.org/jira/browse/JELLY-226
Project: jelly
Type: Wish
Components: core / taglib.core, taglib.jsl, taglib.xml
Reporter: Lukas Theussl
I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 release (see http://jira.codehaus.org/browse/MAVEN-1345 and http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part of the problem seems to be some kind of binary incompatibility in project dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 and jaxen-1.1-beta-8 but failed due to several broken test cases, in particular in the jsl tag library. It would be nice if we had a jelly release with unified dependencies, even though I am not sure it will solve our problem of dropped CDATA sections that I described in JAXEN-67.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (JELLY-226) Upgrade dom4j and jaxen
Posted by "Brett Porter (JIRA)" <co...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12361558 ]
Brett Porter commented on JELLY-226:
------------------------------------
I'd be more comfortable after so much broke between 1.1-beta-4 and beta-6 to know that it wasn't going to change :)
> Upgrade dom4j and jaxen
> -----------------------
>
> Key: JELLY-226
> URL: http://issues.apache.org/jira/browse/JELLY-226
> Project: jelly
> Type: Wish
> Components: core / taglib.core, taglib.jsl, taglib.xml
> Reporter: Lukas Theussl
>
> I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 release (see http://jira.codehaus.org/browse/MAVEN-1345 and http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part of the problem seems to be some kind of binary incompatibility in project dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 and jaxen-1.1-beta-8 but failed due to several broken test cases, in particular in the jsl tag library. It would be nice if we had a jelly release with unified dependencies, even though I am not sure it will solve our problem of dropped CDATA sections that I described in JAXEN-67.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (JELLY-226) Upgrade dom4j and jaxen
Posted by "Paul Libbrecht (JIRA)" <co...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12378851 ]
Paul Libbrecht commented on JELLY-226:
--------------------------------------
The current dependency is jaxen 1.1-beta8 and dom4j 1.5.
Is that sufficient for you ?
Do you need 1.5.2 or 1.6 ?
paul
> Upgrade dom4j and jaxen
> -----------------------
>
> Key: JELLY-226
> URL: http://issues.apache.org/jira/browse/JELLY-226
> Project: Jelly
> Type: Wish
> Components: core / taglib.core, taglib.jsl, taglib.xml
> Reporter: Lukas Theussl
>
> I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 release (see http://jira.codehaus.org/browse/MAVEN-1345 and http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part of the problem seems to be some kind of binary incompatibility in project dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 and jaxen-1.1-beta-8 but failed due to several broken test cases, in particular in the jsl tag library. It would be nice if we had a jelly release with unified dependencies, even though I am not sure it will solve our problem of dropped CDATA sections that I described in JAXEN-67.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (JELLY-226) Upgrade dom4j and jaxen
Posted by "peter royal (JIRA)" <co...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12361557 ]
peter royal commented on JELLY-226:
-----------------------------------
Is Jaxen 1.1. a blocker? The 1.1 beta series is light-years better than 1.0 was, and we're very slowly moving towards 1.1
> Upgrade dom4j and jaxen
> -----------------------
>
> Key: JELLY-226
> URL: http://issues.apache.org/jira/browse/JELLY-226
> Project: jelly
> Type: Wish
> Components: core / taglib.core, taglib.jsl, taglib.xml
> Reporter: Lukas Theussl
>
> I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 release (see http://jira.codehaus.org/browse/MAVEN-1345 and http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part of the problem seems to be some kind of binary incompatibility in project dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 and jaxen-1.1-beta-8 but failed due to several broken test cases, in particular in the jsl tag library. It would be nice if we had a jelly release with unified dependencies, even though I am not sure it will solve our problem of dropped CDATA sections that I described in JAXEN-67.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (JELLY-226) Upgrade dom4j and jaxen
Posted by "Paul Libbrecht (JIRA)" <co...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12379153 ]
Paul Libbrecht commented on JELLY-226:
--------------------------------------
Well... I have now made a few tests and, up to two lines of fixes in jelly-tags-jsl, I seem to be running fine all tag-libs with dom4j-1.6.1...
I would be ready to consider upgrade to dom4j 1.6.1.
paul
> Upgrade dom4j and jaxen
> -----------------------
>
> Key: JELLY-226
> URL: http://issues.apache.org/jira/browse/JELLY-226
> Project: Jelly
> Type: Wish
> Components: core / taglib.core, taglib.jsl, taglib.xml
> Reporter: Lukas Theussl
>
> I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 release (see http://jira.codehaus.org/browse/MAVEN-1345 and http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part of the problem seems to be some kind of binary incompatibility in project dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 and jaxen-1.1-beta-8 but failed due to several broken test cases, in particular in the jsl tag library. It would be nice if we had a jelly release with unified dependencies, even though I am not sure it will solve our problem of dropped CDATA sections that I described in JAXEN-67.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (JELLY-226) Upgrade dom4j and jaxen
Posted by "peter royal (JIRA)" <co...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12361559 ]
peter royal commented on JELLY-226:
-----------------------------------
understood. i'll push for a stable release of jaxen.
> Upgrade dom4j and jaxen
> -----------------------
>
> Key: JELLY-226
> URL: http://issues.apache.org/jira/browse/JELLY-226
> Project: jelly
> Type: Wish
> Components: core / taglib.core, taglib.jsl, taglib.xml
> Reporter: Lukas Theussl
>
> I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 release (see http://jira.codehaus.org/browse/MAVEN-1345 and http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part of the problem seems to be some kind of binary incompatibility in project dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 and jaxen-1.1-beta-8 but failed due to several broken test cases, in particular in the jsl tag library. It would be nice if we had a jelly release with unified dependencies, even though I am not sure it will solve our problem of dropped CDATA sections that I described in JAXEN-67.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (JELLY-226) Upgrade dom4j and jaxen
Posted by "Lukas Theussl (JIRA)" <co...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12378924 ]
Lukas Theussl commented on JELLY-226:
-------------------------------------
Please read the recent comments at http://jira.codehaus.org/browse/MAVEN-1345 (hey, you opened this one! ;) ), I have currently resolved (AFAICT) all problems with dom4j/jaxen in Maven by using a development/branch version of dom4j (unfortunately with the current cvs problems on sourceforge it doesn't seem like this will be released too soon). The only issue I see here is the licensing problem pointed out by E.R. Harold: you shouldn't use any dom4j earlier than 1.5.2.
Cheers,
Lukas
> Upgrade dom4j and jaxen
> -----------------------
>
> Key: JELLY-226
> URL: http://issues.apache.org/jira/browse/JELLY-226
> Project: Jelly
> Type: Wish
> Components: core / taglib.core, taglib.jsl, taglib.xml
> Reporter: Lukas Theussl
>
> I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 release (see http://jira.codehaus.org/browse/MAVEN-1345 and http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part of the problem seems to be some kind of binary incompatibility in project dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 and jaxen-1.1-beta-8 but failed due to several broken test cases, in particular in the jsl tag library. It would be nice if we had a jelly release with unified dependencies, even though I am not sure it will solve our problem of dropped CDATA sections that I described in JAXEN-67.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (JELLY-226) Upgrade dom4j and jaxen
Posted by "Brett Porter (JIRA)" <co...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12361556 ]
Brett Porter commented on JELLY-226:
------------------------------------
this is the ongoing gump failures.
I'm not sure we can upgrade until Jaxen 1.1 is released.
> Upgrade dom4j and jaxen
> -----------------------
>
> Key: JELLY-226
> URL: http://issues.apache.org/jira/browse/JELLY-226
> Project: jelly
> Type: Wish
> Components: core / taglib.core, taglib.jsl, taglib.xml
> Reporter: Lukas Theussl
>
> I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 release (see http://jira.codehaus.org/browse/MAVEN-1345 and http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part of the problem seems to be some kind of binary incompatibility in project dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 and jaxen-1.1-beta-8 but failed due to several broken test cases, in particular in the jsl tag library. It would be nice if we had a jelly release with unified dependencies, even though I am not sure it will solve our problem of dropped CDATA sections that I described in JAXEN-67.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (JELLY-226) Upgrade dom4j and jaxen
Posted by "Paul Libbrecht (JIRA)" <co...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12415443 ]
Paul Libbrecht commented on JELLY-226:
--------------------------------------
Is now committed... looks like i need to wait to see gump take it up.
> Upgrade dom4j and jaxen
> -----------------------
>
> Key: JELLY-226
> URL: http://issues.apache.org/jira/browse/JELLY-226
> Project: Commons Jelly
> Type: Wish
> Components: core / taglib.core, taglib.jsl, taglib.xml
> Reporter: Lukas Theussl
>
> I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 release (see http://jira.codehaus.org/browse/MAVEN-1345 and http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part of the problem seems to be some kind of binary incompatibility in project dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 and jaxen-1.1-beta-8 but failed due to several broken test cases, in particular in the jsl tag library. It would be nice if we had a jelly release with unified dependencies, even though I am not sure it will solve our problem of dropped CDATA sections that I described in JAXEN-67.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (JELLY-226) Upgrade dom4j and jaxen
Posted by "dion gillard (JIRA)" <co...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12379161 ]
dion gillard commented on JELLY-226:
------------------------------------
Looks good!
> Upgrade dom4j and jaxen
> -----------------------
>
> Key: JELLY-226
> URL: http://issues.apache.org/jira/browse/JELLY-226
> Project: Jelly
> Type: Wish
> Components: core / taglib.core, taglib.jsl, taglib.xml
> Reporter: Lukas Theussl
>
> I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 release (see http://jira.codehaus.org/browse/MAVEN-1345 and http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part of the problem seems to be some kind of binary incompatibility in project dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 and jaxen-1.1-beta-8 but failed due to several broken test cases, in particular in the jsl tag library. It would be nice if we had a jelly release with unified dependencies, even though I am not sure it will solve our problem of dropped CDATA sections that I described in JAXEN-67.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org