[ http://jira.codehaus.org/browse/MCHANGES-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249056#action_249056 ]
Lukas Theussl commented on MCHANGES-190: ---------------------------------------- I don't agree with 2. I think the most transparent way *is* to change the XSD. However, I would like to see your proposed implementation first, if you can come up with an solution that doesn't need a new xsd and that satisfies everyone, I will happily accept it. :) > HTML in changes.xml stopped working > ----------------------------------- > > Key: MCHANGES-190 > URL: http://jira.codehaus.org/browse/MCHANGES-190 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: changes.xml > Affects Versions: 2.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_17 > OS name: "linux" version: "2.6.32-686" arch: "i386" Family: "unix" > Reporter: Christian Schulte > Priority: Critical > Attachments: changes.xml, changes.xml, MCHANGES-190.zip > > > The fix for MCHANGES-189 does not seem to be correct. A changes.xml file > containing HTML-Tags got rendered correctly using version 2.2. Starting with > version 2.3, HTML-Tags will be encoded using HTML entities for the '<' and > '>' characters leading to the actual tags getting shown in the report. See > the attached example changes.xml file containing HTML no longer working with > version 2.3. -- 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