I'm looking at the binary-release target, trying to identify the required targets to run in order to IDEnize and mavenize an SDK from sources.
- setup-binary-release (yes and no: we don't want to clean /in, but we want to set the localized.jars property to true) - main (yes) - frameworks-rsls (maybe?) - sample-themes (maybe?) - checkintests (no) - doc (no) - other.locales (yes, otherwise mavenized SDK will fail to resolve dependencies for some -rb.swc artifacts) - binary-package (no) - additional-packages (maybe, isn't the ant tasks jar bundled with the IDEnized sdk?) So Unfortunately, there's no way to set the localized.jars property without also clearing the /in folder, I'd need to add one or two targets to the build.xml in my sandbox, or externally force the value of the localized.jars from the ant command line. Anyway, I'd be perfectly happy with english compiler messages - is this the effect of not setting the localized.jars to true? 2013/9/17 Frédéric THOMAS <webdoubl...@hotmail.com> > Maybe yes, know as well there are many other targets, run ant -p to get > them all displayed and be sure to run the IDE script you need from the > sdk/ide folder, I guess as well you will need to create the compiler > locales as well if you're not US but I can't remember the ant build > variable to set, maybe someone else remember otherwise look into the > release target of the build.xml. > > -Fred > > -----Message d'origine----- > De : Cosma Colanicchia [mailto:cosma...@gmail.com] > Envoyé : mardi 17 septembre 2013 17:52 > À : dev@flex.apache.org > Objet : Re: Building SDK from sources and locales support > > Thank you very much, running the other.locales ant target right now.. > maybe we could drop a note about this in the README? > > > 2013/9/17 Frédéric THOMAS <webdoubl...@hotmail.com> > > > The locales are in and are well managed by the Maven converter / > > deployer, use the SDK provided by the Installer or be sure you ran ant > > -other.locale after a standard ant build from the sources to generate > the locales. > > > > -Fred > > > > -----Message d'origine----- > > De : Cosma Colanicchia [mailto:cosma...@gmail.com] Envoyé : mardi 17 > > septembre 2013 17:31 À : dev@flex.apache.org Objet : Building SDK from > > sources and locales support > > > > Hi, I'm trying to build the latest SDK sources - I need to use it in > > Flash Builder and as mavenized artifacts. > > > > I noticed that, in the compiled and "IDEnized" SDK, the > > {sdkhome}/frameworks/locale/... folders don't contain the *_rb.swc > > files, with the exception of the en_US locale. Is this the intended > > behavior? I see that the Adobe 4.6 SDK containes these compiled > > resource bundles for all supported locales. > > > > In README, I read "The Apache Flex SDK defaults to using the en_US > > locale and SDK error messages are by default displayed in American > English". > > Shouldn't the SDK, by default, include all the supported locales, or > > am I misunderstanding the README? > > > > As a side note, I noticed this as a suspect while searching for the > > cause of a "Could not find artifact > > com.adobe.flash.framework:playerglobal:rb.swc:11.1" - seems that the > > pom generated by the mavenizer references it (the > > com.adobe.flex.framework.flex-framework pom), but the related artifact > > was not generated nor deployed by the mavenizer tool. > > > > Any help? TIA > > >
