continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wendy Smoak (JIRA)" <>
Subject [jira] Updated: (CONTINUUM-1689) Bad string replacement of entities in build result
Date Thu, 10 Sep 2009 05:16:31 GMT


Wendy Smoak updated CONTINUUM-1689:

    Affects Version/s: 1.3.4
        Fix Version/s: 1.4.x

Confirmed in 1.3.4 by adding -X to the arguments of a simple project.

For example, instead of 
OS name: "mac os x" version: "10.5.8" arch: "x86_64" Family: "mac"
the output has
OS name: &quot;mac os x&quot; version: &quot;10.5.8&quot; arch: &quot;x86_64&quot;
Family: &quot;mac&quot;


Instead of 
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-clean-plugin:2.2:clean' -->
the output has
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-clean-plugin:2.2:clean' --&gt;

> Bad string replacement of entities in build result
> --------------------------------------------------
>                 Key: CONTINUUM-1689
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: Web - UI
>    Affects Versions: 1.1, 1.3.4
>            Reporter: Baptiste MATHUS
>            Priority: Minor
>             Fix For: 1.4.x
> 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 =&amp;gt; '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 "=&gt;"
> then another pass detects the & although it shouldn't process it anymore, so :
> * second "=&gt;" is in turn converted "=&amp;gt;"
> I guess the correction weight might depend on how those conversion are done. As a lot
of conversions produces an &, maybe encoding & as &amp; 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:
For more information on JIRA, see:


View raw message