You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Stefan H?bner (JIRA)" <ji...@codehaus.org> on 2006/01/31 01:14:06 UTC

[jira] Created: (MNG-2025) POM is still not read using the right encoding

POM is still not read using the right encoding
----------------------------------------------

         Key: MNG-2025
         URL: http://jira.codehaus.org/browse/MNG-2025
     Project: Maven 2
        Type: Bug

  Components: Plugins and Lifecycle  
    Versions: 2.0    
    Reporter: Stefan Hübner
 Assigned to: John Casey 
    Priority: Critical
     Fix For: 2.0.1


IIRC XML standard says that default encoding is UTF-8 for xml files

That can be overriden with 
<?xml version="1.0" encoding="ISO-8859-1"?>

But files without header saved as UTF8 are not parsed in some systems (eg windows, solaris), while files saved as other encoding (I believe it was ansi) break under a Mac mini with yellowdog linux

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNG-2025) POM is still not read using the right encoding

Posted by "Stefan H?bner (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-2025?page=comments#action_57358 ] 

Stefan Hübner commented on MNG-2025:
------------------------------------

This issue is a clone of MNG-1603. Sorry, The Fix Version is not correct due to cloning (I misunderstood this cloning feature slightly.)

My experiences working with encodings is, that Maven actually DOES NOT read model files using the right encoding. It might be true, that the declared encoding is read and attached to the model. But certain field like *description* are read using the default system character set, which isn't the same as the POM's encoding in all cases.

I'll provide test cases both for maven-model and maven-project to demonstrate the problem.

Again, sorry for the misleading issue data by cloning MNG-1603.

Regards,
Stefan

> POM is still not read using the right encoding
> ----------------------------------------------
>
>          Key: MNG-2025
>          URL: http://jira.codehaus.org/browse/MNG-2025
>      Project: Maven 2
>         Type: Bug

>   Components: Plugins and Lifecycle
>     Versions: 2.0
>     Reporter: Stefan Hübner
>     Assignee: John Casey
>     Priority: Critical
>      Fix For: 2.0.1

>
>
> IIRC XML standard says that default encoding is UTF-8 for xml files
> That can be overriden with 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> But files without header saved as UTF8 are not parsed in some systems (eg windows, solaris), while files saved as other encoding (I believe it was ansi) break under a Mac mini with yellowdog linux

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Updated: (MNG-2025) POM is still not read using the right encoding

Posted by "Stefan H?bner (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2025?page=all ]

Stefan Hübner updated MNG-2025:
-------------------------------

    Attachment: MNG-2025-maven-project-testcases.patch

> POM is still not read using the right encoding
> ----------------------------------------------
>
>          Key: MNG-2025
>          URL: http://jira.codehaus.org/browse/MNG-2025
>      Project: Maven 2
>         Type: Bug

>   Components: Plugins and Lifecycle
>     Versions: 2.0
>     Reporter: Stefan Hübner
>     Assignee: John Casey
>     Priority: Critical
>      Fix For: 2.0.1
>  Attachments: MNG-2025-maven-model-testcases.patch, MNG-2025-maven-project-testcases.patch
>
>
> IIRC XML standard says that default encoding is UTF-8 for xml files
> That can be overriden with 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> But files without header saved as UTF8 are not parsed in some systems (eg windows, solaris), while files saved as other encoding (I believe it was ansi) break under a Mac mini with yellowdog linux

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Updated: (MNG-2025) POM is still not read using the right encoding

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2025?page=all ]

Brett Porter updated MNG-2025:
------------------------------

      Assign To:     (was: John Casey)
    Fix Version:     (was: 2.0.1)

> POM is still not read using the right encoding
> ----------------------------------------------
>
>          Key: MNG-2025
>          URL: http://jira.codehaus.org/browse/MNG-2025
>      Project: Maven 2
>         Type: Bug

>   Components: Plugins and Lifecycle
>     Versions: 2.0
>     Reporter: Stefan Hübner
>     Priority: Critical
>  Attachments: MNG-2025-maven-model-testcases.patch, MNG-2025-maven-project-testcases.patch
>
>
> IIRC XML standard says that default encoding is UTF-8 for xml files
> That can be overriden with 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> But files without header saved as UTF8 are not parsed in some systems (eg windows, solaris), while files saved as other encoding (I believe it was ansi) break under a Mac mini with yellowdog linux

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Updated: (MNG-2025) POM is still not read using the right encoding

Posted by "Stefan H?bner (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2025?page=all ]

Stefan Hübner updated MNG-2025:
-------------------------------

    Attachment: MNG-2025-maven-model-testcases.patch

> POM is still not read using the right encoding
> ----------------------------------------------
>
>          Key: MNG-2025
>          URL: http://jira.codehaus.org/browse/MNG-2025
>      Project: Maven 2
>         Type: Bug

>   Components: Plugins and Lifecycle
>     Versions: 2.0
>     Reporter: Stefan Hübner
>     Assignee: John Casey
>     Priority: Critical
>      Fix For: 2.0.1
>  Attachments: MNG-2025-maven-model-testcases.patch
>
>
> IIRC XML standard says that default encoding is UTF-8 for xml files
> That can be overriden with 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> But files without header saved as UTF8 are not parsed in some systems (eg windows, solaris), while files saved as other encoding (I believe it was ansi) break under a Mac mini with yellowdog linux

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org