[
http://jira.codehaus.org/browse/MEV-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229227#action_229227
]
Joerg Schaible commented on MEV-667:
------------------------------------
Actually there are quite some files in the repo with this problem. When fixing
plexus-utils-1.0.4 manually, the XML parser chokes now about
plexus-container-default-1.0-alpha-8.pom because of the exactly same reason.
And I bet there are a lot more ...
> plexus-utils-1.0.4.pom contains no valid XML
> --------------------------------------------
>
> Key: MEV-667
> URL: http://jira.codehaus.org/browse/MEV-667
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid POM
> Reporter: Joerg Schaible
>
> plexus-utils-1.0.4.pom contains an 'ø' in Tryvge's last name. However,
> the file declares no XML header and therefore a conforming XML parser handles
> the file as UTF-8. Unfortunately this character imples an ISO-8859-1
> encoding. This character is the reason why quite all the Apache commons
> builds of the last years fail with strange errors, if build with IBM JDK 1.4
> or 1.5. Building with jamvm 1.5.4 revealed now at least for me the reason:
> {noformat}
> [WARNING] POM for 'org.codehaus.plexus:plexus-utils:pom:1.0.4:runtime' is
> invalid. It will be ignored for
> artifact resolution. Reason: Parse error reading POM. Reason: TEXT must be
> immediately followed by END_TAG
> and not START_TAG (position: START_TAG seen ...<name>Trygve
> Laugst\ufffdname>\n <email>... @116:14)
> for project org.codehaus.plexus:plexus-utils at
> /home/joehni/.m2/repository/org/codehaus/plexus/plexus-
> utils/1.0.4/plexus-utils-1.0.4.pom
> {noformat}
> So either add an XML header with correct encoding or fix the file encoding.
--
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
