You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Luc Maisonobe (JIRA)" <ji...@apache.org> on 2009/09/15 20:04:59 UTC

[jira] Commented: (COMMONSSITE-43) Parent POM should define encoding

    [ https://issues.apache.org/jira/browse/COMMONSSITE-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755612#action_12755612 ] 

Luc Maisonobe commented on COMMONSSITE-43:
------------------------------------------

This was discussed in this thread: [http://markmail.org/message/5uki2wynb5ffs4mw]

At that time, all people who have contributed to the discussion agreed. However, I don't know if anybody has checked whether some files did depend on the current encoding specification which is ISO-8859-1 (latin 1). Another point is if the javadoc and the source xref generated pages do support UTF-8. I remember encoding problems in maven-generated sites some time ago.

> Parent POM should define encoding
> ---------------------------------
>
>                 Key: COMMONSSITE-43
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-43
>             Project: Commons All
>          Issue Type: Bug
>          Components: Commons Parent Pom
>            Reporter: Sebb
>
> The parent POM should define the following properties:
>     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
>     <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.