incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric THOMAS <>
Subject Re: AW: Compiler Arguments
Date Fri, 02 Nov 2012 09:36:32 GMT
Hi Chris,

For the 4.8, I use the official 3.1, for the 4.9, I use the 3.1 / 3.4 
indifferently but yes, I have to add manualy the corresponding airglobal.swc 
if I want to use the generator against it.

-----Message d'origine----- 
Sent: Friday, November 02, 2012 9:55 AM
Subject: AW: Compiler Arguments

Hi Frederic,

which version would be the one you would have liked to see there?
The versions I use are the defaults, you can surely allways override the 
versions used by providing a dependendyManagement section to your poms or by 
explicitly adding the corresponding airglobal.swc.


Von: Frédéric THOMAS []
Gesendet: Freitag, 2. November 2012 00:37
Betreff: Re: Compiler Arguments

oups, I thought you updated the air version but no :P

-----Message d'origine-----
From: Frédéric THOMAS
Sent: Friday, November 02, 2012 12:23 AM
Subject: Re: AW: AW: AW: AW: AW: Compiler Arguments

Good news, especialy for the themes, I've seen as well from the dump file
you reported that you updated the air version to the one of the sdk, I
reported this change manualy in the generator but I did it quickly, hard
coding the version number which is bad, I hope you'll send me a copy as soon
as you'll finish. For the namespace, I stayed on com.adobe as otherwize I've
been in trouble with some exlusions, I hope I won't run into this problem
anymore with the new version.

-----Message d'origine-----
Sent: Thursday, November 01, 2012 11:53 PM
Subject: AW: AW: AW: AW: AW: Compiler Arguments

Well I did a lot of little stuff.
- I re-activated the creation oft he config-zip, but left out the themes
- I finally activated generating the lib-artifacts with their real versions
(This is what's causing quite some trouble in FM but without it the FDKs
wouldn't be 100% correct)
- Now I copy every swc theme and compile every non-swc theme to a swc-theme
so all themes are now swc themes
- Apache FDKs are generated into the Apache namespace "org.apache.flex"
- There were a few glitches with the poms generated for air application ...
now all should be good :-)

Still 2 tests failling in the testsuite, but I simply have to find a way to
automatically get the version of the framework.swc in a given lib. Shouldn't
be that hard using my dependency-management extra-poms. So hopefully I'll be
able to finish everything on Sunday.


-----Ursprüngliche Nachricht-----
Von: Frédéric THOMAS []
Gesendet: Donnerstag, 1. November 2012 23:17
Betreff: Re: AW: AW: AW: AW: Compiler Arguments


What kind of changes did you do in the generator ? If they are importants,
I'll be happy to get a fresh copy.

For the Apache Con Europe, unfortunatly, I can't (I have to work).

-----Message d'origine-----
Sent: Thursday, November 01, 2012 10:35 PM
Subject: AW: AW: AW: AW: Compiler Arguments

Am I understanding you correctly, that the handling of "-compiler.locale" is
correct that way, but the "-metadata.language" should probably only contain
the first segment (In this case " es_MX")?
Sounds sensible. Think I'll have a look at why this is some times generated.

@Mike ... I get failures about every 10 runs of the entire Testsuite (And
yes ... having to run it that often really sucks ... but I want to have my
new FDKs up and running)

By the way ... I did do quite some work on the Flexmojos6 and FDK Generator
on the last few days and I think I might be able to finish FM6 and the new
Flex FDKs before going zo the Apache Con Europe :-) (See you there?)


-----Ursprüngliche Nachricht-----
Von: Alex Harui []
Gesendet: Donnerstag, 1. November 2012 21:57
Betreff: Re: AW: AW: AW: Compiler Arguments

On 11/1/12 1:17 PM, "" <>

> Nope,
> This would be the case if you wanted to add 3 different locales.
> If you define es_MX,es_ES,en_US this is more a locale-chain (I reverse
> learned this from the unit-test code.
Hmm, is there really a difference from in the SDK code-paths for this?  I
didn't think there was, but I'm not the expert on locales.

Anyway, I want to point out your error is not in the locale handling.  The
arguments to -locale look like they are being handled correctly, but
somehow, the same list ends up in -metadata.language.  How is that
happening?  If it is automatically being set up by something, that might
need to be changed to create a single string.

Alex Harui
Flex SDK Team
Adobe Systems, Inc. 

View raw message