You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/06/29 11:19:08 UTC
[jira] Created: (MAVEN-1345) XML Output is non-well-formed
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1345
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1345
Summary: XML Output is non-well-formed
Type: Bug
Status: Unassigned
Priority: Critical
Original Estimate: 1 hour
Time Spent: Unknown
Remaining: 1 hour
Project: maven
Components:
core
Versions:
1.0-rc3
Assignee:
Reporter: Paul Libbrecht
Created: Tue, 29 Jun 2004 5:18 AM
Updated: Tue, 29 Jun 2004 5:18 AM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1345) Upgrade to dom4j 1.6
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_39276 ]
Brett Porter commented on MAVEN-1345:
-------------------------------------
no fix for the cdata bug in sight, and upgrading to jaxen 1.1-beta-6 made things go downhill (see the failure in gump of the jelly xml tag library - this affects basically every maven plugin in existence).
I don't really have time to bugger around with this any more, so I'm
going to see if the dom4j 1.4 release will work as before. My main
concern with sticking with 1.4-dev-8 is that there is no way to locate
the sources.
We can live with the bugs in 1.4 (as we already are).
If anyone with some knowledge of dom4j and jaxen wants to put their hand
up to work through it and get up to dom4j 1.6/jaxen 1.1, please say so.
> Upgrade to dom4j 1.6
> --------------------
>
> Key: MAVEN-1345
> URL: http://jira.codehaus.org/browse/MAVEN-1345
> Project: maven
> Type: Bug
> Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 1.1-beta-1
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1345) Upgrade to dom4j 1.4
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_53878 ]
Brett Porter commented on MAVEN-1345:
-------------------------------------
If its the Aelfred2 parser, we don't use it. We can surgically remove it from the JAR. The dom4j project should also ask us to retract or update the releases from ibiblio.
> Upgrade to dom4j 1.4
> --------------------
>
> Key: MAVEN-1345
> URL: http://jira.codehaus.org/browse/MAVEN-1345
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Reopened: (MAVEN-1345) Upgrade to dom4j 1.4
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1345?page=all ]
Brett Porter reopened MAVEN-1345:
---------------------------------
Elliotte - can you please elaborate on what the issues are. We can't use dom4j 1.5.2 because it is not backwards compatible and I was unable to get it to work with Jelly.
> Upgrade to dom4j 1.4
> --------------------
>
> Key: MAVEN-1345
> URL: http://jira.codehaus.org/browse/MAVEN-1345
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MAVEN-1345) Upgrade to dom4j 1.4
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1345?page=all ]
Brett Porter closed MAVEN-1345:
-------------------------------
Resolution: Fixed
> Upgrade to dom4j 1.4
> --------------------
>
> Key: MAVEN-1345
> URL: http://jira.codehaus.org/browse/MAVEN-1345
> Project: maven
> Type: Bug
> Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 1.1-beta-1
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1345) Upgrade to dom4j 1.4
Posted by "Elliotte Rusty Harold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_54708 ]
Elliotte Rusty Harold commented on MAVEN-1345:
----------------------------------------------
The AElfred parser is indeed the problem I was referring to. If you pull it out of the JAR file, dom4j 1.4 should be license-kosher.
if you've shipped this previosuly yourseld you shoudl probably delete or replace those archives when you get a minure.
> Upgrade to dom4j 1.4
> --------------------
>
> Key: MAVEN-1345
> URL: http://jira.codehaus.org/browse/MAVEN-1345
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Reopened: (MAVEN-1345) Upgrade to dom4j 1.5
Posted by ji...@codehaus.org.
Message:
The following issue has been reopened.
Reopener: Brett Porter
Date: Tue, 25 Jan 2005 5:50 PM
I knew it was too good to be true... a lot of the JSL stuff is behaving strangely. Need to fix that, and also check xdoc still works with Maven 1.0.x.
Problems so far:
- CDATA content seems to be ignored instead of picked up as text(), even though doing it in the JSL test suite works (maybe it was inadvertantly using dom4j 1.4 through the running maven)
- some of the $nav stuff (menu headers and links) are not rendered, but their children are (for links, through the wrong template)
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1345
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1345
Summary: Upgrade to dom4j 1.5
Type: Bug
Status: Reopened
Priority: Critical
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.1-beta-1
Versions:
1.0-rc3
Assignee: Brett Porter
Reporter: Paul Libbrecht
Created: Tue, 29 Jun 2004 5:18 AM
Updated: Tue, 25 Jan 2005 5:50 PM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1345) Upgrade to dom4j 1.4
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1345?page=all ]
Brett Porter updated MAVEN-1345:
--------------------------------
Fix Version: (was: 1.1-beta-1)
1.1-beta-3
> Upgrade to dom4j 1.4
> --------------------
>
> Key: MAVEN-1345
> URL: http://jira.codehaus.org/browse/MAVEN-1345
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MAVEN-1345) Upgrade to dom4j 1.5
Posted by ji...@codehaus.org.
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Tue, 25 Jan 2005 9:12 AM
this went smoothly... a little TOO smoothly if you ask me :)
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1345
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1345
Summary: Upgrade to dom4j 1.5
Type: Bug
Status: Closed
Priority: Critical
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.1-beta-1
Versions:
1.0-rc3
Assignee: Brett Porter
Reporter: Paul Libbrecht
Created: Tue, 29 Jun 2004 5:18 AM
Updated: Tue, 25 Jan 2005 9:12 AM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1345) Upgrade to dom4j 1.4
Posted by "Elliotte Rusty Harold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_53816 ]
Elliotte Rusty Harold commented on MAVEN-1345:
----------------------------------------------
Please do not use dom4j 1.4 or earlier. It has some license issues that weren't corrected until about 1.6. I have to check on the exact version, but I'm pretty sure 1.4 is too early to contain the fix.
OK. I checked. 1.5.2 is the first version that's kosher. You really shouldn't use anything earlier.
> Upgrade to dom4j 1.4
> --------------------
>
> Key: MAVEN-1345
> URL: http://jira.codehaus.org/browse/MAVEN-1345
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 1.1-beta-1
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1345) Upgrade to dom4j 1.5
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Brett Porter (mailto:brett@codehaus.org)
Date: Tue, 31 Aug 2004 2:00 AM
Comment:
upgrade to dom4j 1.5 and see what breaks. We need to do this because Jelly has also upgraded and we are using CVS HEAD there in 1.1
Changes:
summary changed from XML Output is non-well-formed to Upgrade to dom4j 1.5
timeoriginalestimate changed from 3600
timeestimate changed from 1 hour
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MAVEN-1345?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1345
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1345
Summary: Upgrade to dom4j 1.5
Type: Bug
Status: Open
Priority: Critical
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.1
Versions:
1.0-rc3
Assignee: Brett Porter
Reporter: Paul Libbrecht
Created: Tue, 29 Jun 2004 5:18 AM
Updated: Tue, 31 Aug 2004 2:00 AM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1345) Upgrade to dom4j 1.4
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_54704 ]
Brett Porter commented on MAVEN-1345:
-------------------------------------
We should just stay on 1.4, at least until Jaxen releases 1.1 and Jelly upgrades.
> Upgrade to dom4j 1.4
> --------------------
>
> Key: MAVEN-1345
> URL: http://jira.codehaus.org/browse/MAVEN-1345
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1345) Upgrade to dom4j 1.4
Posted by "Kohsuke Kawaguchi (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_55945 ]
Kohsuke Kawaguchi commented on MAVEN-1345:
------------------------------------------
dom4j 1.4 causes MPXDOC-188 (and MPXDOC-38.) (note that even though they are marked as closed, the issue isn't fixed yet.)
> Upgrade to dom4j 1.4
> --------------------
>
> Key: MAVEN-1345
> URL: http://jira.codehaus.org/browse/MAVEN-1345
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1345) Upgrade to dom4j 1.4
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1345?page=all ]
Brett Porter updated MAVEN-1345:
--------------------------------
Environment:
Description:
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.
was:
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.
Summary: Upgrade to dom4j 1.4 (was: Upgrade to dom4j 1.6)
> Upgrade to dom4j 1.4
> --------------------
>
> Key: MAVEN-1345
> URL: http://jira.codehaus.org/browse/MAVEN-1345
> Project: maven
> Type: Bug
> Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 1.1-beta-1
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1345) Upgrade to dom4j 1.4
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_53877 ]
Lukas Theussl commented on MAVEN-1345:
--------------------------------------
I suppose it is the use of the Aelfred2 parser that was removed in the 1.5.2 release (http://www.dom4j.org/changes-report.html#1_5_2).
But I have to agree with Brett, this is a complete blocker for us if CDATA sections are being swallowed. If we can't use it for licensing issues, what alternatives would we have?
> Upgrade to dom4j 1.4
> --------------------
>
> Key: MAVEN-1345
> URL: http://jira.codehaus.org/browse/MAVEN-1345
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1345) XML Output is non-well-formed
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Brett Porter (mailto:brett@codehaus.org)
Date: Fri, 23 Jul 2004 2:04 AM
Changes:
Fix Version changed to 1.1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MAVEN-1345?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1345
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1345
Summary: XML Output is non-well-formed
Type: Bug
Status: Open
Priority: Critical
Original Estimate: 1 hour
Time Spent: Unknown
Remaining: 1 hour
Project: maven
Components:
core
Fix Fors:
1.1
Versions:
1.0-rc3
Assignee: Brett Porter
Reporter: Paul Libbrecht
Created: Tue, 29 Jun 2004 5:18 AM
Updated: Fri, 23 Jul 2004 2:04 AM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1345) Upgrade to dom4j 1.6
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Brett Porter (mailto:brett@codehaus.org)
Date: Thu, 10 Feb 2005 8:17 PM
Comment:
only the CDATA issue remaining. See JAXEN-67.
Other bug has been fixed post 1.5.2, so will need a 1.6 release of dom4j to use it.
Changes:
summary changed from Upgrade to dom4j 1.5 to Upgrade to dom4j 1.6
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MAVEN-1345?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1345
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1345
Summary: Upgrade to dom4j 1.6
Type: Bug
Status: Reopened
Priority: Critical
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.1-beta-1
Versions:
1.0-rc3
Assignee: Brett Porter
Reporter: Paul Libbrecht
Created: Tue, 29 Jun 2004 5:18 AM
Updated: Thu, 10 Feb 2005 8:17 PM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org