Please vote for the promotion of l10n plugin from the sandbox:
+1, any plugin out of the sandbox is less hassle for uses to use it and
provide feedback.
Before the actual release, somebody could take care of these:
Both mojos use j.l.String instead of j.i.File for file parameters and are
therefore subject to relative path issues.
The status report has a user-accessible parameter taking model.Resource
which is a further source of relative paths and needs manual resolving (like
in MRESOURCES-32).
It seems odd that the l10n:pseudo operates on "target/classes" (hence taking
generated/filtered resources into account) while l10n:report by default only
operates on the static resources in "src/main/resources" etc.
The plugin's own localization support should be completed
(L10NStatusReport.java:559)
A sample report from the plugin about its own bundles would be a nice
addition to its own site docs. I guess we could find some cute guys to add
further bundles to make it more interesting ;-)
Checkstyle errors could be fixed. Especially the report's renderBody() might
benefit from refactoring out the analysis stuff from the actual report
generation.
Benjamin
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
