You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Christian Schulte (JIRA)" <ji...@codehaus.org> on 2009/02/11 18:13:19 UTC
[jira] Created: (CONTINUUM-2072) Take care of the platform's
default encoding when building continuum
Take care of the platform's default encoding when building continuum
--------------------------------------------------------------------
Key: CONTINUUM-2072
URL: http://jira.codehaus.org/browse/CONTINUUM-2072
Project: Continuum
Issue Type: Bug
Affects Versions: 1.3.1
Reporter: Christian Schulte
When building continuum-1.3.1, the platform's default encoding is used when copying resources. If this platform encoding is something like LANG="C", lots of german umlauts will get converted to question marks.
...
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
...
Umlauts are ok with continuum 1.2.3 but not with 1.3.1! I think it should be sufficient to add a corresponding encoding to the resources plugin or just use an UTF-8 platform encoding when building continuum releases (export LANG=en_US.UTF-8 before building).
--
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] Commented: (CONTINUUM-2072) Take care of the platform's
default encoding when building continuum
Posted by "Christian Schulte (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165125#action_165125 ]
Christian Schulte commented on CONTINUUM-2072:
----------------------------------------------
export LANG=en_US.UTF-8 not only before building, also before doing the svn checkout cause subversion also uses the platform's default encoding, I think.
> Take care of the platform's default encoding when building continuum
> --------------------------------------------------------------------
>
> Key: CONTINUUM-2072
> URL: http://jira.codehaus.org/browse/CONTINUUM-2072
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.1
> Reporter: Christian Schulte
>
> When building continuum-1.3.1, the platform's default encoding is used when copying resources. If this platform encoding is something like LANG="C", lots of german umlauts will get converted to question marks.
> ...
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> ...
> Umlauts are ok with continuum 1.2.3 but not with 1.3.1! I think it should be sufficient to add a corresponding encoding to the resources plugin or just use an UTF-8 platform encoding when building continuum releases (export LANG=en_US.UTF-8 before building).
--
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] Commented: (CONTINUUM-2072) Take care of the platform's
default encoding when building continuum
Posted by "Jose Morales Martinez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165156#action_165156 ]
Jose Morales Martinez commented on CONTINUUM-2072:
--------------------------------------------------
I think this issue is related to CONTINUUM-2053. It was fixed in 1.3.2.
problems continue in this version?
> Take care of the platform's default encoding when building continuum
> --------------------------------------------------------------------
>
> Key: CONTINUUM-2072
> URL: http://jira.codehaus.org/browse/CONTINUUM-2072
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.1
> Reporter: Christian Schulte
>
> When building continuum-1.3.1, the platform's default encoding is used when copying resources. If this platform encoding is something like LANG="C", lots of german umlauts will get converted to question marks.
> ...
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> ...
> Umlauts are ok with continuum 1.2.3 but not with 1.3.1! I think it should be sufficient to add a corresponding encoding to the resources plugin or just use an UTF-8 platform encoding when building continuum releases (export LANG=en_US.UTF-8 before building).
--
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: (CONTINUUM-2072) Take care of the platform's default
encoding when building continuum
Posted by "Christian Schulte (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schulte closed CONTINUUM-2072.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.3.2
Verified by building continuum trunk.
export LANG="C"
svn checkout ...
mvn install
./continuum start
works, as well as
export LANG="en_US.UTF-8"
svn checkout ...
mvn install
./continuum start
> Take care of the platform's default encoding when building continuum
> --------------------------------------------------------------------
>
> Key: CONTINUUM-2072
> URL: http://jira.codehaus.org/browse/CONTINUUM-2072
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.1
> Reporter: Christian Schulte
> Fix For: 1.3.2
>
>
> When building continuum-1.3.1, the platform's default encoding is used when copying resources. If this platform encoding is something like LANG="C", lots of german umlauts will get converted to question marks.
> ...
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> ...
> Umlauts are ok with continuum 1.2.3 but not with 1.3.1! I think it should be sufficient to add a corresponding encoding to the resources plugin or just use an UTF-8 platform encoding when building continuum releases (export LANG=en_US.UTF-8 before building).
--
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