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 14:32:32 UTC

[jira] Created: (MANTRUN-155) Encoding issue with created build-main.xml

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

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

        

[jira] Updated: (MANTRUN-155) Encoding issue with created build-main.xml

Posted by "Anders Hammar (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MANTRUN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anders Hammar updated MANTRUN-155:
----------------------------------

    Attachment: mantrun-155.patch

Attached is a patch. I've integrated the reproducing project as an IT.

If there's an encoding issue with the actual patch, the test string (in the ant target of the pom) should be "non-ASCII chars: ÅÄÖ".

For the fix, I've also updated the code to add a correct xml header specifying the encoding. Please review that!


> 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.patch, 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

       

[jira] Closed: (MANTRUN-155) Encoding issue with created build-main.xml

Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MANTRUN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier closed MANTRUN-155.
-----------------------------

    Resolution: Fixed

Fixed in [r1004461|http://svn.apache.org/viewvc?view=revision&revision=1004461].  Thanks for the patch!

> 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
>            Assignee: Paul Gier
>             Fix For: 1.6
>
>         Attachments: antrun_error.log, mantrun-155.patch, 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

        

[jira] Updated: (MANTRUN-155) Encoding issue with created build-main.xml

Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MANTRUN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated MANTRUN-155:
------------------------------

    Fix Version/s: 1.6
         Assignee: Paul Gier

> 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
>            Assignee: Paul Gier
>             Fix For: 1.6
>
>         Attachments: antrun_error.log, mantrun-155.patch, 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

        

[jira] Updated: (MANTRUN-155) Encoding issue with created build-main.xml

Posted by "Anders Hammar (JIRA)" <ji...@codehaus.org>.
     [ 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