[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
