[
http://jira.codehaus.org/browse/MRELEASE-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MRELEASE-201.
--------------------------------------
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.0-beta-8
Fixed by MRELEASE-87. While the entities are still expanded by the Release
Plugin, they are now properly encoded as given by the XML declaration (which is
kept now).
> Deployed POM is not valid XML
> -----------------------------
>
> Key: MRELEASE-201
> URL: http://jira.codehaus.org/browse/MRELEASE-201
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Reporter: Joerg Schaible
> Assignee: Benjamin Bentmann
> Fix For: 2.0-beta-8
>
> Attachments: MNG-2362.zip
>
>
> If the POM has utf-8 encoding and you make usage of entities to support
> extended characters, these characters are no longer encoded as entities in
> the repository (well, the effect is already visible in
> target/effective-pom.xml). This is not a rule of general, POMs with packaging
> "pom" are installed and deployed correctly.
> Multi module example. The attached archive contains a parent POM and a POM
> for a jar. Both UTF-8 encoded POMs contain a developer with a name using an
> entitiy. Releasing the POMs they are written with the expanded entitiy making
> the XML invalid.
--
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
