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/18 14:18:40 UTC

[jira] Created: (MECLIPSE-56) Generated .project-file misses encoding declaration

Generated .project-file misses encoding declaration
---------------------------------------------------

         Key: MECLIPSE-56
         URL: http://jira.codehaus.org/browse/MECLIPSE-56
     Project: Maven 2.x Eclipse Plugin
        Type: Bug

    Versions: 2.0    
    Reporter: Stefan Hübner


Hi,

I'm experiencing problems creating eclipse project files, if the project's description in pom.xml contains special characters like german umlauts (like "öüä"). Refreshing the eclipse workspace after running eclipse:eclipse results in the following message from eclipse:

"Errors occurred while refreshing resources with the local file system.
  Failed to read the project description file (.project) for comworld-eventlisteners.  The file has been changed on disk, and it now contains invalid information.  The project will not function properly until the description file is restored to a valid state."

This is caused by the content of the .project's generated comment-tag containing the exact same description as in pom.xml. But the .project-file is generated without stating an encoding parser should use to read it. So, if I prepend the line
   <?xml version="1.0" encoding="ISO-8859-15"?>
eclipse is able to read the file just fine.

Regards,
Stefan

-- 
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: (MECLIPSE-56) Generated .project-file misses encoding declaration

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

Stefan Hübner commented on MECLIPSE-56:
---------------------------------------

I would suggest that the eclipse plugin always encodes generated {{.project}}-files to UTF-8. Furthermore those {{.project}}-files should contain a xml-prolog declaring the used encoding (i.e. UTF-8).

> Generated .project-file misses encoding declaration
> ---------------------------------------------------
>
>          Key: MECLIPSE-56
>          URL: http://jira.codehaus.org/browse/MECLIPSE-56
>      Project: Maven 2.x Eclipse Plugin
>         Type: Bug

>     Versions: 2.0
>     Reporter: Stefan Hübner
>  Attachments: MECLIPSE-56-maven-eclipse-plugin.patch1, MECLIPSE-56-resourcesForAdditionalTestcaseszip
>
>
> Hi,
> I'm experiencing problems creating eclipse project files, if the project's description in pom.xml contains special characters like german umlauts (like "öüä"). Refreshing the eclipse workspace after running eclipse:eclipse results in the following message from eclipse:
> "Errors occurred while refreshing resources with the local file system.
>   Failed to read the project description file (.project) for comworld-eventlisteners.  The file has been changed on disk, and it now contains invalid information.  The project will not function properly until the description file is restored to a valid state."
> This is caused by the content of the .project's generated comment-tag containing the exact same description as in pom.xml. But the .project-file is generated without stating an encoding parser should use to read it. So, if I prepend the line
>    <?xml version="1.0" encoding="ISO-8859-15"?>
> eclipse is able to read the file just fine.
> Regards,
> Stefan

-- 
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: (MECLIPSE-56) Generated .project-file misses encoding declaration

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

Stefan Hübner commented on MECLIPSE-56:
---------------------------------------

Sorry, attached {{MECLIPSE-56-maven-eclipse-plugin.patch1}} was meant here

> Generated .project-file misses encoding declaration
> ---------------------------------------------------
>
>          Key: MECLIPSE-56
>          URL: http://jira.codehaus.org/browse/MECLIPSE-56
>      Project: Maven 2.x Eclipse Plugin
>         Type: Bug

>     Versions: 2.0
>     Reporter: Stefan Hübner
>  Attachments: MECLIPSE-56-maven-eclipse-plugin.patch1, MECLIPSE-56-resourcesForAdditionalTestcaseszip
>
>
> Hi,
> I'm experiencing problems creating eclipse project files, if the project's description in pom.xml contains special characters like german umlauts (like "öüä"). Refreshing the eclipse workspace after running eclipse:eclipse results in the following message from eclipse:
> "Errors occurred while refreshing resources with the local file system.
>   Failed to read the project description file (.project) for comworld-eventlisteners.  The file has been changed on disk, and it now contains invalid information.  The project will not function properly until the description file is restored to a valid state."
> This is caused by the content of the .project's generated comment-tag containing the exact same description as in pom.xml. But the .project-file is generated without stating an encoding parser should use to read it. So, if I prepend the line
>    <?xml version="1.0" encoding="ISO-8859-15"?>
> eclipse is able to read the file just fine.
> Regards,
> Stefan

-- 
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: (MECLIPSE-56) Generated .project-file misses encoding declaration

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

Stefan Hübner updated MECLIPSE-56:
----------------------------------

    Attachment: MECLIPSE-56-resourcesForAdditionalTestcaseszip

> Generated .project-file misses encoding declaration
> ---------------------------------------------------
>
>          Key: MECLIPSE-56
>          URL: http://jira.codehaus.org/browse/MECLIPSE-56
>      Project: Maven 2.x Eclipse Plugin
>         Type: Bug

>     Versions: 2.0
>     Reporter: Stefan Hübner
>  Attachments: MECLIPSE-56-resourcesForAdditionalTestcaseszip
>
>
> Hi,
> I'm experiencing problems creating eclipse project files, if the project's description in pom.xml contains special characters like german umlauts (like "öüä"). Refreshing the eclipse workspace after running eclipse:eclipse results in the following message from eclipse:
> "Errors occurred while refreshing resources with the local file system.
>   Failed to read the project description file (.project) for comworld-eventlisteners.  The file has been changed on disk, and it now contains invalid information.  The project will not function properly until the description file is restored to a valid state."
> This is caused by the content of the .project's generated comment-tag containing the exact same description as in pom.xml. But the .project-file is generated without stating an encoding parser should use to read it. So, if I prepend the line
>    <?xml version="1.0" encoding="ISO-8859-15"?>
> eclipse is able to read the file just fine.
> Regards,
> Stefan

-- 
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: (MECLIPSE-56) Generated .project-file misses encoding declaration

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

Stefan Hübner updated MECLIPSE-56:
----------------------------------

    Attachment: MECLIPSE-56-maven-eclipse-plugin.patch1

> Generated .project-file misses encoding declaration
> ---------------------------------------------------
>
>          Key: MECLIPSE-56
>          URL: http://jira.codehaus.org/browse/MECLIPSE-56
>      Project: Maven 2.x Eclipse Plugin
>         Type: Bug

>     Versions: 2.0
>     Reporter: Stefan Hübner
>  Attachments: MECLIPSE-56-maven-eclipse-plugin.patch1, MECLIPSE-56-resourcesForAdditionalTestcaseszip
>
>
> Hi,
> I'm experiencing problems creating eclipse project files, if the project's description in pom.xml contains special characters like german umlauts (like "öüä"). Refreshing the eclipse workspace after running eclipse:eclipse results in the following message from eclipse:
> "Errors occurred while refreshing resources with the local file system.
>   Failed to read the project description file (.project) for comworld-eventlisteners.  The file has been changed on disk, and it now contains invalid information.  The project will not function properly until the description file is restored to a valid state."
> This is caused by the content of the .project's generated comment-tag containing the exact same description as in pom.xml. But the .project-file is generated without stating an encoding parser should use to read it. So, if I prepend the line
>    <?xml version="1.0" encoding="ISO-8859-15"?>
> eclipse is able to read the file just fine.
> Regards,
> Stefan

-- 
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: (MECLIPSE-56) Generated .project-file misses encoding declaration

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

Stefan Hübner updated MECLIPSE-56:
----------------------------------

    Attachment: MECLIPSE-56-maven-eclipse-plugin.patch2

> Generated .project-file misses encoding declaration
> ---------------------------------------------------
>
>          Key: MECLIPSE-56
>          URL: http://jira.codehaus.org/browse/MECLIPSE-56
>      Project: Maven 2.x Eclipse Plugin
>         Type: Bug

>     Versions: 2.0
>     Reporter: Stefan Hübner
>  Attachments: MECLIPSE-56-maven-eclipse-plugin.patch1, MECLIPSE-56-maven-eclipse-plugin.patch2, MECLIPSE-56-resourcesForAdditionalTestcaseszip
>
>
> Hi,
> I'm experiencing problems creating eclipse project files, if the project's description in pom.xml contains special characters like german umlauts (like "öüä"). Refreshing the eclipse workspace after running eclipse:eclipse results in the following message from eclipse:
> "Errors occurred while refreshing resources with the local file system.
>   Failed to read the project description file (.project) for comworld-eventlisteners.  The file has been changed on disk, and it now contains invalid information.  The project will not function properly until the description file is restored to a valid state."
> This is caused by the content of the .project's generated comment-tag containing the exact same description as in pom.xml. But the .project-file is generated without stating an encoding parser should use to read it. So, if I prepend the line
>    <?xml version="1.0" encoding="ISO-8859-15"?>
> eclipse is able to read the file just fine.
> Regards,
> Stefan

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