You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anders Hammar (JIRA)" <ji...@codehaus.org> on 2010/10/01 20:58:32 UTC
[jira] Updated: (MANTRUN-155) Encoding issue with created
build-main.xml
[ http://jira.codehaus.org/browse/MANTRUN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anders Hammar updated MANTRUN-155:
----------------------------------
Attachment: mantrun-155.zip
Attached a test project that reproduces this issue on MacOS 10.6.4, with Mac Java 1.6.0 and Maven 3.0-RC3. I haven't tested, but it should also reproduce on Windows.
> Encoding issue with created build-main.xml
> ------------------------------------------
>
> Key: MANTRUN-155
> URL: http://jira.codehaus.org/browse/MANTRUN-155
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
> Affects Versions: 1.5
> Environment: Windows XP SP2
> Sun JDK 1.6.0_16
> Maven 3.0-RC2
> Reporter: Anders Hammar
> Attachments: antrun_error.log, mantrun-155.zip
>
>
> Having non-ASCII chars in the antrun configuration breaks the build. The reason seems to be that the created build-main.xml is in the os default encoding, while the project is configured with another encoding. It works with m-antrun-p v1.4.
> I've attached a log of the error message.
> Could this issue be related to the refactoring done in MANTRUN-142?
--
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