You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2006/04/13 17:46:48 UTC

[jira] Updated: (MAVEN-1345) Upgrade to dom4j 1.4

     [ http://jira.codehaus.org/browse/MAVEN-1345?page=all ]

Lukas Theussl updated MAVEN-1345:
---------------------------------

     Priority: Blocker  (was: Critical)
    Assign To: Lukas Theussl  (was: Brett Porter)
         type: Task  (was: Bug)

Yes, I left a request at the link above, but didn't get a response yet. I'm thinking about putting our own version on ibiblio, I have tested it since my comment above and haven't found any issues. WDYT?

I'm putting this to blocker status now as we have to resolve at least the licensing issue and also to mark it as something we _really_ have to fix for beta-3 (contrary to most of what is scheduled now ;) ). Note that if we manage to upgrade dom4j, we have to publish new versions of the changes and xdoc plugins which will need a dependency on jaxen too because of API changes in dom4j. :(

> Upgrade to dom4j 1.4
> --------------------
>
>          Key: MAVEN-1345
>          URL: http://jira.codehaus.org/browse/MAVEN-1345
>      Project: Maven
>         Type: Task

>   Components: core
>     Versions: 1.0-rc3
>     Reporter: Paul Libbrecht
>     Assignee: Lukas Theussl
>     Priority: Blocker
>      Fix For: 1.1-beta-3

>
>
> Currently, Maven relies on dom4j beta 8.
> This is bad in many respects, the worst being that the XML output, for example provided by Jelly XML plugin, has wrong xmlns attributes.
> At least the 1.5 betas of dom4j all fix this, they also fix the html output which was, otherwise, inserting random (kind-of) spaces in the text.

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