Return-Path: 
 <flex-dev-return-13985-apmail-incubator-flex-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 244AAD7D1
	for <apmail-incubator-flex-dev-archive@minotaur.apache.org>;
 Fri,  2 Nov 2012 12:34:34 +0000 (UTC)
Received: (qmail 99731 invoked by uid 500); 2 Nov 2012 12:34:33 -0000
Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org
Received: (qmail 99518 invoked by uid 500); 2 Nov 2012 12:34:32 -0000
Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:flex-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:flex-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:flex-dev@incubator.apache.org>
List-Id: <flex-dev.incubator.apache.org>
Reply-To: flex-dev@incubator.apache.org
Delivered-To: mailing list flex-dev@incubator.apache.org
Received: (qmail 99494 invoked by uid 99); 2 Nov 2012 12:34:32 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2012 12:34:32 +0000
X-ASF-Spam-Status: No, hits=1.0 required=5.0
	tests=FRT_ADOBE2,RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of webdoublefx@hotmail.com
 designates 65.55.111.92 as permitted sender)
Received: from [65.55.111.92] (HELO blu0-omc2-s17.blu0.hotmail.com)
 (65.55.111.92)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2012 12:34:24 +0000
Received: from BLU162-DS4 ([65.55.111.71]) by blu0-omc2-s17.blu0.hotmail.com
 with Microsoft SMTPSVC(6.0.3790.4675);
	 Fri, 2 Nov 2012 05:34:03 -0700
X-Originating-IP: [82.247.153.175]
X-EIP: [/HxHvGCg5Xw9cQ+QyPGg+cXyCvIrO38m]
X-Originating-Email: [webdoublefx@hotmail.com]
Message-ID: <BLU162-ds4F1592BE060BC05FEB883B4670@phx.gbl>
From: =?iso-8859-1?Q?Fr=E9d=E9ric_THOMAS?= <webdoublefx@hotmail.com>
To: <flex-dev@incubator.apache.org>
References: 
 <66E38C42347D6446BF7FCB22C3D3878072E0695C52@ECCR06PUBLIC.exchange.local>
 <CCB8302B.47E9D%aharui@adobe.com>
 <66E38C42347D6446BF7FCB22C3D3878072E0695C55@ECCR06PUBLIC.exchange.local>
 <BLU162-ds13F23AD06E4DF027C8E421B4600@phx.gbl>
 <66E38C42347D6446BF7FCB22C3D3878072E0695C56@ECCR06PUBLIC.exchange.local>
 <BLU162-ds1059690EFDD3F57D153414B4600@phx.gbl>,<BLU162-ds18E54A53DDAE97EC41FB72B4600@phx.gbl>
 <66E38C42347D6446BF7FCB22C3D3878072E075599C@ECCR06PUBLIC.exchange.local>
 <BLU162-ds1037C815A8E494CCD43B1AB4670@phx.gbl>,<BLU162-ds7D92ACB3F78B95293B239B4670@phx.gbl>
 <66E38C42347D6446BF7FCB22C3D3878072E075599F@ECCR06PUBLIC.exchange.local>,<BLU162-ds282723E0B86F5BEE5AB50B4670@phx.gbl>
 <66E38C42347D6446BF7FCB22C3D3878072E07559A0@ECCR06PUBLIC.exchange.local>,<BLU162-ds718F9932117DD2E99A93AB4670@phx.gbl>
 <66E38C42347D6446BF7FCB22C3D3878072E07559A1@ECCR06PUBLIC.exchange.local>
In-Reply-To: 
 <66E38C42347D6446BF7FCB22C3D3878072E07559A1@ECCR06PUBLIC.exchange.local>
Subject: Re: AW: AW: AW: Compiler Arguments
Date: Fri, 2 Nov 2012 13:34:00 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3505.912
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912
X-OriginalArrivalTime: 02 Nov 2012 12:34:03.0273 (UTC)
 FILETIME=[577A9790:01CDB8F6]
X-Virus-Checked: Checked by ClamAV on apache.org

Maybe you can guess which version to use from 2 maps I found :

in the FLEXSDK/framework/build.xml  :

<target name="playerglobal-setswfversion" description="Set the swfversion to 
insert into the flex config file">
        <condition property="playerglobal.swfversion" value="11">
            <equals arg1="${playerglobal.version}" arg2="10.2" />
        </condition>
        <condition property="playerglobal.swfversion" value="12">
            <equals arg1="${playerglobal.version}" arg2="10.3" />
        </condition>
        <condition property="playerglobal.swfversion" value="13">
            <equals arg1="${playerglobal.version}" arg2="11.0" />
        </condition>
        <condition property="playerglobal.swfversion" value="14">
            <equals arg1="${playerglobal.version}" arg2="11.1" />
        </condition>
        <condition property="playerglobal.swfversion" value="15">
            <equals arg1="${playerglobal.version}" arg2="11.2" />
        </condition>
        <condition property="playerglobal.swfversion" value="16">
            <equals arg1="${playerglobal.version}" arg2="11.3" />
        </condition>
        <condition property="playerglobal.swfversion" value="17">
            <equals arg1="${playerglobal.version}" arg2="11.4" />
        </condition>
    </target>

In the AIRSDK/airsdk.xml :

    <applicationNamespaces>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/3.4</descriptorNamespace>
            <swfVersion>17</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/3.3</descriptorNamespace>
            <swfVersion>16</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/3.2</descriptorNamespace>
            <swfVersion>15</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/3.1</descriptorNamespace>
            <swfVersion>14</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/3.0</descriptorNamespace>
            <swfVersion>13</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/2.7</descriptorNamespace>
            <swfVersion>12</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/2.6</descriptorNamespace>
            <swfVersion>11</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/2.5</descriptorNamespace>
            <swfVersion>10</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/2.0</descriptorNamespace>
            <swfVersion>10</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/1.5.3</descriptorNamespace>
            <swfVersion>10</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/1.5.2</descriptorNamespace>
            <swfVersion>10</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/1.5.1</descriptorNamespace>
            <swfVersion>10</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/1.5</descriptorNamespace>
            <swfVersion>10</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/1.1</descriptorNamespace>
            <swfVersion>10</swfVersion>
        </versionMap>
        <versionMap>
            <descriptorNamespace>http://ns.adobe.com/air/application/1.0</descriptorNamespace>
            <swfVersion>10</swfVersion>
        </versionMap>
    </applicationNamespaces>


The common denominator is the swfVersion.
And from what I'm reading, before playerglobal 10.2, I can use the air 2.5 
because it uses the swf-version 10, am I wrong ?


-----Message d'origine----- 
From: christofer.dutz@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 
anything there, it would fallback to the checksum method.

Chris

PS: Anybody know the Air versions needed in Flex:
- 3.0.0.447A
- 3.0.1.1732A
- 3.2.0.3958A

________________________________________
Von: Fr�d�ric THOMAS [webdoublefx@hotmail.com]
Gesendet: Freitag, 2. November 2012 11:49
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: Compiler Arguments

It's not difficult to add, maybe only a new property in the build.properties
would be even enough, you matter if it is repported in the generated
flex-config.xml ? if it's yes, I can modify the build.xml relatively if you
want and if that's ok for the commiters.

-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Friday, November 02, 2012 11:20 AM
To: flex-dev@incubator.apache.org
Subject: AW: AW: Compiler Arguments

Yup ... added a README.txt to the Generator code explaining stuff like that
... I would have prefered to have this information provided in an official
flex/air descriptor though ... same as the flash player version in the
flex-config.xml

Chris

________________________________________
Von: Fr�d�ric THOMAS [webdoublefx@hotmail.com]
Gesendet: Freitag, 2. November 2012 11:16
An: flex-dev@incubator.apache.org
Betreff: Re: AW: Compiler Arguments

Ok, I've got it.
Working on the trunk, develop branch or using the
apache-flex-sdk-4.8.0-incubating-bin.zip, folks will have to had it manualy
to the frameworks\libs\air to be able to use the generator then, right ?


-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Friday, November 02, 2012 11:02 AM
To: flex-dev@incubator.apache.org
Subject: AW: Compiler Arguments

Well as you had a look at the generator ... I have two directories as input
to the generator. One directory containing all Air SDKs and one containing
all Flex SDKs ... first I process all Air SDKs and generate the needed
artifacts from that ... while doing so I calculate the checksumms of the
airglobals that are then used for finding out the Air version used in a Flex
SDK. Unfortunately ich couldn't find out which Air versions the first 3
Flex3 versions are using, but I didn't waste too much time in finding out,
currently you simply can't build Air application with those really old FDKs.

Chris

________________________________________
Von: Fr�d�ric THOMAS [webdoublefx@hotmail.com]
Gesendet: Freitag, 2. November 2012 10:57
An: flex-dev@incubator.apache.org
Betreff: Re: Compiler Arguments

Well, actually, what I did in the generator is to define where is the air
sdk I want to use, in the main function I have generator.generateAllAir(new
File(sdkSourceDirectory, "air"), sdkTargetDirectory);
but I haven't got the same file structure than yours, you're more generic if
I remember well.

When you said "The generator used to find out which version by comparing the
checksum of the airglobal.swc with the checksums of the airglobals bundled
in the Air fdks ", where is the location of the airglobal.swc you use to
comparate the checksum ?

-----Message d'origine-----
From: Fr�d�ric THOMAS
Sent: Friday, November 02, 2012 10:36 AM
To: flex-dev@incubator.apache.org
Subject: Re: AW: Compiler Arguments

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-----
From: christofer.dutz@c-ware.de
Sent: Friday, November 02, 2012 9:55 AM
To: flex-dev@incubator.apache.org
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.

Chris

________________________________________
Von: Fr�d�ric THOMAS [webdoublefx@hotmail.com]
Gesendet: Freitag, 2. November 2012 00:37
An: flex-dev@incubator.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, 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-----
From: christofer.dutz@c-ware.de
Sent: Thursday, November 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
(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.

Chris


-----Urspr�ngliche Nachricht-----
Von: Fr�d�ric THOMAS [mailto:webdoublefx@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'll be happy to get a fresh copy.

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

-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Thursday, November 01, 2012 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 " 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?)

Chris




-----Urspr�ngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Donnerstag, 1. November 2012 21:57
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: Compiler Arguments




On 11/1/12 1:17 PM, "christofer.dutz@c-ware.de" <christofer.dutz@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 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.
http://blogs.adobe.com/aharui