[
http://jira.codehaus.org/browse/MCHANGES-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230409#action_230409
]
Jörg Hohwiller commented on MCHANGES-190:
-----------------------------------------
IMHO adding markup as text in CDATA sections was always a hack.
The best way to fix this would be to allow xsd:any in action and put the
content as is in the result.
Then we also do not need a trigger as commented in
"Dennis Lundberg added a comment - 21/Dec/09 2:31 PM"
because one can still have plain text in CDATA and does not need to care about
escaping.
> 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-report
> 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
