[
http://jira.codehaus.org/browse/MCHANGES-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203725#action_203725
]
Dennis Lundberg commented on MCHANGES-190:
------------------------------------------
I think we need to have a configuration parameter for this.
Some people, like me, wants to use the issue text for both the announcement and
the report and can't have html code in the changes.xml file. Others, like
yourself, wants to enhance their issue text with html code and only use it for
the report.
Now we only need to figure out a characteristic name for the parameter and a
good default value. The parameter will go into the changes-report goal. How
about allowHtml with a default value of "false"?
> 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
