Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shiro.apache.org
Date: Fri, 4 Nov 2016 17:01:59 +0000 (UTC)
From: "Brian Demers (JIRA)" <jira@apache.org>
To: dev@shiro.apache.org
Message-ID: <JIRA.13018017.1478254769000.192111.1478278919183@Atlassian.JIRA>
In-Reply-To: <JIRA.13018017.1478254769000@Atlassian.JIRA>
References: <JIRA.13018017.1478254769000@Atlassian.JIRA> <JIRA.13018017.1478254769550@arcas>
Subject: [jira] [Reopened] (SHIRO-599) Fix file encoding warnings during
 maven build and reporting
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 04 Nov 2016 17:02:00 -0000


     [ https://issues.apache.org/jira/browse/SHIRO-599?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Demers reopened SHIRO-599:
--------------------------------
      Assignee: Brian Demers

> 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=C3=B6rn Raupach
>            Assignee: Brian Demers
>            Priority: Minor
>
> The maven build emits several warnings that the file encoding has not bee=
n set.
> bq. File encoding has not been set, using platform encoding UTF-8, i.e. b=
uild is platform dependent! The file encoding for reports output files shou=
ld 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)