commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "peter royal (JIRA)" <>
Subject [jira] Commented: (JELLY-226) Upgrade dom4j and jaxen
Date Mon, 02 Jan 2006 23:08:07 GMT
    [ ] 

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:
>      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 and 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:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message