Resource bundles dependency

[GoogleCodeExporter]

Improve resource bundle resolution algorithm.

* Must not be required inform the locale on classifier.
* Must look for locales specified on pom.xml
* locale default value must be current_Locale if a translation is available
or en_US if none found.

VELO

Original issue reported on code.google.com by velo...@gmail.com on 5 Jun 2008 at 4:34

[GoogleCodeExporter]

This has suddenly bumped up on the priority list for us. We're now building 10 
locales across a dozen libraries, 
and managing dependencies is a huge pain. We have 116 dependency entries in our 
main app and adding or 
removing a locale or a dependency is a huge manual tedious task.

If you don't have time to do this right now, any quick thoughts on how you 
intended to implement this. I may 
start work on it.

Original comment by RedB...@gmail.com on 1 Aug 2008 at 7:59

[GoogleCodeExporter]

Well, my original idea is to change resource-bundle file association from swc 
to rb.swc.

Then, install on repo a dummy file-1.0.rb.swc to use as beacon, and install real
locale files using the locale as classifier file-1.0-en_US.rb.swc

A pom will only point to resource-bundle, without any classifier.  At runtime
flex-mojos will take every resource-bundle available and will resolve all 
locales at
runtime.  If any one was not found throw an exception.

Am I clear?

I'm sure I can't do this until 8/15

VELO

Original comment by velo...@gmail.com on 1 Aug 2008 at 8:11

[GoogleCodeExporter]

That's clear enough to get started. I'll see how it goes.

Original comment by RedB...@gmail.com on 1 Aug 2008 at 8:53

[GoogleCodeExporter]

Fixed at revision 683

Original comment by velo...@gmail.com on 20 Aug 2008 at 3:03

• Changed state: Fixed