Request to support mulitple resource bundles per project

[GoogleCodeExporter]

Which version of the plugin are you using? 1.6

What steps will reproduce the problem?
1. Create a new resource bundle project, with multiple resource bundle names 
(e.g. one.properties, two.properties), each with localized translations to 
multiple target languages (e.g. one_de.properties, one_fr.properties, 
two_de.properties, two_fr.properties).
2. Run the validate target.
3. Observe that properties defined in one.properties (and it's corresponding 
local language analogs) are logged as warnings because they are not localized 
in two.properties (and it's corresponding local language analogs).

What would be the expected output?
It would be nice if the resource bundles were treated separately, so that 
one(__*).properties files were analyzed, then two(_*).properties files were 
compared completely independently.  That allows segregation of translations 
into multiple smaller (and perhaps easier to manage/digest/understand) files.

Original issue reported on code.google.com by patrick....@gmail.com on 29 May 2013 at 6:15

[GoogleCodeExporter]

I agree with you. Current behavior of 
com.googlecode.l10nmavenplugin.validators.orchestrator.DirectoryValidator is to 
consider that all *.properties files of a directory are part of the same bundle.
But as mentioned ResourceBundle naming convention would allow to use smarter 
filter based on bundle name.

Original comment by romain.q...@gmail.com on 30 May 2013 at 10:36

[GoogleCodeExporter]

Original comment by romain.q...@gmail.com on 2 Jun 2013 at 1:50

• Changed state: Started
• Added labels: Milestone-1.7

[GoogleCodeExporter]

Original comment by romain.q...@gmail.com on 14 Nov 2013 at 10:28

• Changed state: Fixed