You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2018/04/22 21:38:00 UTC

[jira] [Commented] (MRESOURCES-247) Improve message warning

    [ https://issues.apache.org/jira/browse/MRESOURCES-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447381#comment-16447381 ] 

Karl Heinz Marbaise commented on MRESOURCES-247:
------------------------------------------------

What about a message with a link to the FAQ:
{code}
[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!
[WARNING] Please take a look into FAQ: https://maven.apache.org/general.html#encoding-warning
 {code}

> Improve message warning
> -----------------------
>
>                 Key: MRESOURCES-247
>                 URL: https://issues.apache.org/jira/browse/MRESOURCES-247
>             Project: Maven Resources Plugin
>          Issue Type: Improvement
>    Affects Versions: 3.0.2
>            Reporter: Michel Barret
>            Priority: Trivial
>
> When a maven display message like "File encoding has not been set", it can be usefull to display what is the name of configuration to fix it. Instead:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!
> {code}
> we can have:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!
> [WARNING] Maybe you should set the configuration: project.reporting.outputEncoding
> {code}
>  
> {{It can be usefull!}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)