[jira] Closed: (MSITE-104) There is no way to specify the input encoding of site documents

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MSITE-104?page=all ]
     
Brett Porter closed MSITE-104:
------------------------------

     Assign To: Brett Porter
    Resolution: Fixed

applied with modifications:
- a FNFE was ignored, so I removed that and let it propogate as it used to
- the unsupported excoding was logged and ignored, which would have rendered an empty site. Propogated as an IOException
- removed the deprecated method since we can still break the API in this alpha state without affecting other software
- removed additional logging of parameters in the site mojo.

> There is no way to specify the input encoding of site documents 
> ----------------------------------------------------------------
>
>          Key: MSITE-104
>          URL: http://jira.codehaus.org/browse/MSITE-104
>      Project: Maven 2.x Site Plugin
>         Type: Bug

>     Reporter: Naoki Nose
>     Assignee: Brett Porter
>      Fix For: 2.0-beta-5
>  Attachments: doxia-input-encoding.diff, maven-site-plugin-input-encoding.diff
>
>
> In Japan,it's necessary to specify the input encoding of site document different from the system default,
> because there is two commonly used encodings in Japanese environment(Shift_JIS and EUC-JP).
> But current maven-site-plugin doesn't provide the way to specify the input encoding of site documents explicitly.
> We need to specify it in POM.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira