You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/27 22:47:10 UTC
[jira] (SUREFIRE-1120) Improved warning message "File encoding has
not been set, ..."
[ https://jira.codehaus.org/browse/SUREFIRE-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated SUREFIRE-1120:
-------------------------------------
Summary: Improved warning message "File encoding has not been set, ..." (was: Improved Warning message "File encoding has not been set, ...")
> Improved warning message "File encoding has not been set, ..."
> --------------------------------------------------------------
>
> Key: SUREFIRE-1120
> URL: https://jira.codehaus.org/browse/SUREFIRE-1120
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.18
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Fix For: 2.19
>
>
> The following warning message
> "[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!"
> will be updated in SUREFIRE 2.19 in order to extend the hint with POM property configuration.
> "[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent! The character encoding for reports output files should be referenced by POM property ${project.reporting.outputEncoding}."
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)