Well I think as you specified your locale settings with a wrong element name the default locale is used and this is en_US. While building the compiler reads the MetaData tag declaring use of a resource bundle called fapda, but will not find it. That's why it's complaining and after configuring the locale settings correctly it won't use the default and therefore find your properties.
Hope that explains it :-) Chris 2011/8/4 Giorgio Vespucci <[email protected]>: > Christofer, Pawel, thank you very much > It seems to work :) > > Thanks to Christofer hint I have been able to download en_US and fr_FR > artifacts. > Regarding es_ES, I found this old thread: > http://osdir.com/ml/flex-mojos/2010-08/msg00011.html > It seems that spanish flash-integration and playerglobal are not distributed > by repositories :( > > Using Pawel hint I have been able to workaround this es_ES issue. In fact I > can see: > ... > [INFO] Resolved resource bundle for > 'com.adobe.flex.framework:flash-integration:rb.swc:4.1.0.16248:compile' > using localization chain. The 'en_US' will be used to build the missing > 'es_ES' > ... > [INFO] Resolved resource bundle for > 'com.adobe.flex.framework:playerglobal:rb.swc:4.1.0.16248:compile' using > localization chain. The 'en_US' will be used to build the missing 'es_ES'... > ... > > Now I have a couple of questions for you, if you please :) > > 1) Since the es_ES artifacts are not found in repositories it seems they are > re-resolved at every build. Is it correct? > > 2) I thought the problem was that flex-mojos couldn't find _my_ locale files > under default path ${basedir}/src/main/locales/{locale}. > My project is named fapda and I have a fapda.properties for each locale, so > I had the Error: Unable to find resource bundle 'fapda' for locale 'en_US' > message. > Now it seems that "unblocking" the localization mechanism thanks to both > your hints, my properties has been correctly loaded, for all the locale I > set in pom. > Could you explain me how can it be? (Sorry for the complex question) > > Thank you > On Wed, Aug 3, 2011 at 4:30 PM, pawel <[email protected]> wrote: >> >> It also might be a problem of lacking resource for particular locale. >> I had that issue with sdk resources, like 'rpc' missing for some >> exotic locales. In that case you might use locale chains, like that: >> >> <localesCompiled> >> <locale>en_US</locale> >> <locale>es_ES,en_US</locale> >> <locale>fr_FR,en_US</locale> >> </localesCompiled> >> >> In that case, if there are missing resource from particular locale, >> then it will look for this resource in next locale from the list. >> >> > > -- > Giorgio Vespucci > giorgio [dot] vespucci [at] gmail [dot] com > Skype, Twitter, Slideshare: gvespucci > http://xpermanwalking.blogspot.com > > -- > You received this message because you are subscribed to the Google > Groups "Flex Mojos" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/flex-mojos > > http://flexmojos.sonatype.org/ > -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/
