You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Croydon Dias (JIRA)" <ji...@codehaus.org> on 2011/07/21 04:47:42 UTC
[jira] Created: (SUREFIRE-757) Project encoding properties is not
checked
Project encoding properties is not checked
------------------------------------------
Key: SUREFIRE-757
URL: https://jira.codehaus.org/browse/SUREFIRE-757
Project: Maven Surefire
Issue Type: Bug
Components: Maven Failsafe Plugin
Affects Versions: 2.9
Environment: windows 7 SP1 64bit. CentOS 5.6 64bit
Reporter: Croydon Dias
Priority: Trivial
We do have the file encoding *<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>* set in our parent project properties.
We added the failsafe plugin for our integration tests and start seeing the following warning message
On Windows - *[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!*
On CentOS - *[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!*
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-757) Project encoding properties is not checked
Posted by "Doreen Becker (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296201#comment-296201 ]
Doreen Becker commented on SUREFIRE-757:
----------------------------------------
Use the additional property for reporting output:
{code}
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
{code}
> Project encoding properties is not checked
> ------------------------------------------
>
> Key: SUREFIRE-757
> URL: https://jira.codehaus.org/browse/SUREFIRE-757
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
> Affects Versions: 2.9
> Environment: windows 7 SP1 64bit. CentOS 5.6 64bit
> Reporter: Croydon
> Priority: Trivial
>
> We do have the file encoding *<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>* set in our parent project properties.
> We added the failsafe plugin for our integration tests and start seeing the following warning message
> On Windows - *[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!*
> On CentOS - *[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!*
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira