RE: [m2.0.5] maven-release-plugin changes HTML entities

[Jörg Schaible]

Thorsten Heit wrote on Thursday, March 15, 2007 5:28 PM:

> Hi,
> 
> I'm actually evaluating Artifactory as repository proxy/cache
> and today played a bit with the maven-release-plugin
> (2.0-beta-5-SNAPSHOT; more precisely
> maven-release-plugin-2.0-beta-5-20070301.114416-5.jar
> according to my local repository).
> 
> My pom.xml started with the following:
> 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!DOCTYPE xml [<!ENTITY quot "&#34;">
>                <!ENTITY euro "&#x20ac;">
>                <!ENTITY reg "&#174;">
>                <!ENTITY nbsp "&#160;">
>                <!ENTITY Auml "&#196;">
>                <!ENTITY Uuml "&#220;">
>                <!ENTITY Ouml "&#214;">
>                <!ENTITY auml "&#228;">
>                <!ENTITY uuml "&#252;">
>                <!ENTITY ouml "&#246;">
>                <!ENTITY raquo "&#187;">
>                <!ENTITY szlig "&#223;">]>
> <project xmlns="http://maven.apache.org/POM/4.0.0";
>         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>       <modelVersion>4.0.0</modelVersion>
>       <groupId>de.ukv</groupId>
>       <artifactId>maven</artifactId>
>       <version>1.0-SNAPSHOT</version>
>       <name>
>               Voreinstellungen f&uuml;r Maven-basierte Projekte       </name>
> etc.
> 
> "mvn release:prepare" went fine, but "mvn release:perform"
> gave me a return code 500 when Maven finally tried to deploy
> the pom.xml to Artifactory. I could track that down to a bug
> in Artifactory (1.2.0.1) which obviously doesn't like when a
> pom.xml contains umlaut characters.
> 
> When I then looked at my pom.xml I wondered:
> 
> 1) The XML header above wasn't there anymore
> 2) The <project...> header which originally spread over three lines
> was only line. 3) "&uuml;" was changed into an umlaut ("ü")
> 
> 
> Is this normal behaviour or did I just encounter a bug in the
> release plugin? Is it even possible to prevent the plugin
> from changing my pom according to 1-3? I haven't seen much about that
> in the docs at
> http://maven.apache.org/plugins/maven-release-plugin/... 

Known issue: http://jira.codehaus.org/browse/MRELEASE-201

- Jörg

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]