Re: AW: AW: AW: Compiler Arguments
Maybe you can guess which version to use from 2 maps I found :
in the FLEXSDK/framework
ristofer.d...@c-ware.de
Sent: Friday, November 02, 2012 12:15 PM
To: flex-dev@incubator.apache.org
Subject: AW: AW: AW: Compiler Arguments
Well having the AirVersion in the air-config.xml would be great :-) I could
then extend the Generator that it looks at that file and if it doesn't find
or.apache.org
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
To: flex-dev@incubator.apache.org
Subject: Re: AW: AW: AW: AW: AW: Compiler Arguments
Good news, espec
otmail.com]
Gesendet: Freitag, 2. November 2012 00:23
An: flex-dev@incubator.apache.org
Betreff: 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 ch
ber 01, 2012 11:53 PM
To: flex-dev@incubator.apache.org
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
directory
- I finally activated generating the lib-artifacts with their real versions
sprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Gesendet: Donnerstag, 1. November 2012 23:17
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: Compiler Arguments
Chris,
What kind of changes did you do in the generator ? If they are importants, I&#x
: Donnerstag, 1. November 2012 22:54
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: Compiler Arguments
On 11/1/12 2:35 PM, "christofer.d...@c-ware.de"
wrote:
> Am I understanding you correctly, that the handling of
> "-compiler.locale" is correct that wa
012 10:35 PM
To: flex-dev@incubator.apache.org
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
On 11/1/12 2:35 PM, "christofer.d...@c-ware.de"
wrote:
> 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
k I might be able to finish FM6 and the new Flex
FDKs before going zo the Apache Con Europe :-) (See you there?)
Chris
-Ursprüngliche Nachricht-
Von: Alex Harui [mailto:aha...@adobe.com]
Gesendet: Donnerstag, 1. November 2012 21:57
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW:
On 11/1/12 1:17 PM, "christofer.d...@c-ware.de"
wrote:
> 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 SD
nts passed to the compiler in the
execute method of the MxmlcMojo class and didn't see any mention of the
localesRuntimes.
-Message d'origine-
From: christofer.d...@c-ware.de
Sent: Thursday, November 01, 2012 9:17 PM
To: flex-dev@incubator.apache.org
Subject: AW: AW: AW: Comp
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.
Assuming you have 3 locale property files, en_US containing the complete set of
values and only some of them being
13 matches
Mail list logo
