[
http://jira.codehaus.org/browse/CONTINUUM-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Lim updated CONTINUUM-1689:
---------------------------------
Attachment: CONTINUUM-1689.patch
Here's a patch that resolves html encoding issue.
> Bad string replacement of entities in build result
> --------------------------------------------------
>
> Key: CONTINUUM-1689
> URL: http://jira.codehaus.org/browse/CONTINUUM-1689
> Project: Continuum
> Issue Type: Bug
> Components: Web - UI
> Affects Versions: 1.1, 1.3.4 (Beta)
> Reporter: Baptiste MATHUS
> Priority: Minor
> Fix For: Backlog
>
> Attachments: CONTINUUM-1689.patch
>
>
> I just noticed that the output of maven is wrongly encoded. Here's one of
> lines of he generated html source :
> [INFO] Setting property: resource.loader => 'classpath'.
> Remind: In the console, the output is the following (output of mvn site) :
> [INFO] Setting property: resource.loader => 'classpath'.
> As you can see, there's a problem
> I guess the entity conversion is done twice :
> * first "=>" is converted "=>"
> then another pass detects the & although it shouldn't process it anymore, so :
> * second "=>" is in turn converted "=>"
> I guess the correction weight might depend on how those conversion are done.
> As a lot of conversions produces an &, maybe encoding & as & should be
> the very first conversion to be done in the list ?
> Maybe even some "dependency" tree could do the trick (or even better, an API
> that already does that neatly :)).
> Cheers.
> Let me know if you need anything else.
--
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
