[
https://jira.codehaus.org/browse/SUREFIRE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356340#comment-356340
]
Tibor Digana commented on SUREFIRE-757:
---------------------------------------
Perhaps we would run into the consensus if extending the Warning message with a
hint to configure SUREFIRE plugin properly, something like this:
[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e.
build is platform dependent! The character encoding for reports output files
needs to be configured with POM property ${project.reporting.outputEncoding}.
> 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
> Assignee: Tibor Digana
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
