You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/05/13 21:04:12 UTC

[jira] [Commented] (MRESOURCES-220) Encoding example should mention recommended default project.build.sourceEncoding property

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

Hudson commented on MRESOURCES-220:
-----------------------------------

SUCCESS: Integrated in maven-plugins #6002 (See [https://builds.apache.org/job/maven-plugins/6002/])
[MRESOURCES-220] Encoding example should mention recommended default project.build.sourceEncoding property
 o Mentioning the default and the explicit definition
   as an exception. (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1743750])
* maven-resources-plugin/src/site/apt/examples/encoding.apt.vm


> Encoding example should mention recommended default project.build.sourceEncoding property
> -----------------------------------------------------------------------------------------
>
>                 Key: MRESOURCES-220
>                 URL: https://issues.apache.org/jira/browse/MRESOURCES-220
>             Project: Maven Resources Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.7
>         Environment: n/a
>            Reporter: Anders Hammar
>            Assignee: Karl Heinz Marbaise
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> The example "Specifying a character encoding scheme" could be read as one should specify encoding. Typically one should specify the project.build.sourceEncoding property instead and use the same encoding for Java sources and resources.
> This page should mention this best-practice.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)