shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Demers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SHIRO-599) Fix file encoding warnings during maven build and reporting
Date Fri, 04 Nov 2016 15:56:58 GMT

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

Brian Demers commented on SHIRO-599:
------------------------------------

Can you send me a snippet of the build output for the module that causes
the problem ?

On Fri, Nov 4, 2016 at 11:44 AM, Björn Raupach (JIRA) <jira@apache.org>



> Fix file encoding warnings during maven build and reporting
> -----------------------------------------------------------
>
>                 Key: SHIRO-599
>                 URL: https://issues.apache.org/jira/browse/SHIRO-599
>             Project: Shiro
>          Issue Type: Improvement
>            Reporter: Björn Raupach
>            Priority: Minor
>
> The maven build emits several warnings that the file encoding has not been set.
> bq. File encoding has not been set, using platform encoding UTF-8, i.e. build is platform
dependent! The file encoding for reports output files should be provided by the POM property
${project.reporting.outputEncoding}.
> Not sure if all the files are actually in UTF-8. (lets hope). If they are this issue
is easy to fix.
> Add two properties in the properties tag in shiro-root pom.xml
> {code:xml}
> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
> <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
> {code}



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

Mime
View raw message