[
http://jira.codehaus.org/browse/MCLIRR-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann closed MCLIRR-10.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.2
As for the Locale.getDefault(): This is simply following the Maven standard
behaviour. You can convince yourself by looking into the AbstractMavenReport,
which does quite the same. I wouldn't want to implement a different pattern.
Apart from that, I can't see any sense in changing a single reports locale.
Note that the site plugin *does* support multiple locales: See
http://maven.apache.org/guides/mini/guide-site.html Also note, that you can
override the default locale by setting the system properties user.language (for
example fr) and user.country (for example FR).
> adding french properties
> ------------------------
>
> Key: MCLIRR-10
> URL: http://jira.codehaus.org/browse/MCLIRR-10
> Project: Maven 2.x Clirr Plugin
> Issue Type: Improvement
> Environment: GNU/Linux, eclipse 3.1, Sun Java 6
> Reporter: Luc Maisonobe
> Priority: Trivial
> Fix For: 2.2
>
> Attachments: clirr-report_fr.properties
>
>
> Here is a small properties file for report generation in french.
> I noticed the Locale used is retrieved by Locale.getDefault() in
> ClirrReport.execute(). It would be nice to be able to force some value by
> configuring the plugin using something like:
> <reportLocale>en</reportLocale>
> This would allow to publish a report in some locale even if the development
> machine uses another locale (which is my case).
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
