Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of webdoublefx@hotmail.com
 designates 157.55.2.98 as permitted sender)
Message-ID: <DUB118-DS12E289103E6A32A41AE1C3B41D0@phx.gbl>
From: =?iso-8859-1?Q?Fr=E9d=E9ric_THOMAS?= <webdoublefx@hotmail.com>
To: <dev@flex.apache.org>
References: 
 <66E38C42347D6446BF7FCB22C3D3878072E84C18BC@ECCR06PUBLIC.exchange.local>
 <CD2BEF09.4C6A9%aharui@adobe.com>
 <66E38C42347D6446BF7FCB22C3D3878072E8F34462@ECCR06PUBLIC.exchange.local>
 <CACK5iZfYj5QuiDuPPmx9YA-PcvkPV+aYt94=acSXpNtM=ZvWsw@mail.gmail.com>
 <66E38C42347D6446BF7FCB22C3D3878072E983BFB0@ECCR06PUBLIC.exchange.local>
 <DUB118-DS1046DA4B89E5704D39D0A1B41D0@phx.gbl>
 <66E38C42347D6446BF7FCB22C3D3878072E983BFE3@ECCR06PUBLIC.exchange.local>
 <DUB118-DS24FD868B8EC2379AE69EC5B41D0@phx.gbl>
 <66E38C42347D6446BF7FCB22C3D3878072E983C00E@ECCR06PUBLIC.exchange.local>
 <DUB118-DS15EF53B2DF83498608EFB6B41D0@phx.gbl>
 <DUB118-DS22212F1FE09DC7F80CE958B41D0@phx.gbl>
 <66E38C42347D6446BF7FCB22C3D3878072E983C094@ECCR06PUBLIC.exchange.local>
 <DUB118-DS22AD85EBD4B6884E37A000B41D0@phx.gbl>
In-Reply-To: <DUB118-DS22AD85EBD4B6884E37A000B41D0@phx.gbl>
Subject: Re: Splitting up Flex and Air?
Date: Thu, 31 Jan 2013 15:55:58 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 8bit
Importance: Normal

oups :

If ApacheFlexSDK
    for each rsl in rsls
        if rsl.version == sdk.version
            artifactRsl.version = mavenSdk.Version
        else
            artifactRsl.version = rsl.Version
else
    process as today.

-----Message d'origine----- 
From: Fr�d�ric THOMAS
Sent: Thursday, January 31, 2013 3:52 PM
To: dev@flex.apache.org
Subject: Re: AW: Splitting up Flex and Air?

ok, then, does something like this acceptable ?

If ApacheFlexSDK
    for each rsl in rsls
        if rsls.version == sdk.version
            artifactRsl.version = mavenSdk.Version
        else
            artifactRsl.version = rsls.Version
else
    process as today.

-Fred

-----Message d'origine----- 
From: christofer.dutz@c-ware.de
Sent: Thursday, January 31, 2013 3:44 PM
To: dev@flex.apache.org
Subject: AW: Splitting up Flex and Air?

Well I think this would not be correct as OSMF is currently not in version
4.9.xxx, but 2.0
http://sourceforge.net/projects/osmf.adobe/files/
So in my opinion the version number in the Apache FDK is not correct. If the
OSMF would one day reach 4.9 version numbers things would start getting
really ugly cause then there would be repos containing 4.9 versions that are
ages old as well as repos containing the new version.  So I would strongly
suggest only to set the versions of stuff that belongs to us.

Chris


-----Urspr�ngliche Nachricht-----
Von: Fr�d�ric THOMAS [mailto:webdoublefx@hotmail.com]
Gesendet: Donnerstag, 31. Januar 2013 15:27
An: dev@flex.apache.org
Betreff: Re: Splitting up Flex and Air?

To be more precise, I would like to let the code as it is for the Adobe SDKs
and assign the SDK version to the rsls for the Apache SDKs, would it be a
problem ?

-Fred

-----Message d'origine-----
From: Fr�d�ric THOMAS
Sent: Thursday, January 31, 2013 3:14 PM
To: dev@flex.apache.org
Subject: Re: AW: AW: AW: Splitting up Flex and Air?

Hi Chris,

I was happy trying that but it doesn't work, the current implementation
which process rsls, getting the version number of the artifact extracting it
from the original rls file is based on the assumption that Textlayout and
OMSF can have a different version number than the SDK and make it a
generality for all the rsls, which doesn't fit for my attemp.

Even if this assumption is true for the SDK < 4.8, it's apparently not true
for SDK >= 4.8, could we hardcode this as an exception for these 2 libs and
assign the SDK version number for the others ?

-Fred

-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Thursday, January 31, 2013 11:42 AM
To: dev@flex.apache.org
Subject: AW: AW: AW: Splitting up Flex and Air?

Sure I'm fine with that :-)


-----Urspr�ngliche Nachricht-----
Von: Fr�d�ric THOMAS [mailto:webdoublefx@hotmail.com]
Gesendet: Donnerstag, 31. Januar 2013 11:03
An: dev@flex.apache.org
Betreff: Re: AW: AW: Splitting up Flex and Air?

Ok, I don't need to change the AIR version, should work then, anyway, maybe
add a step-by-step help in the readme for the last part as I didn't get
everything :)

Still, do you mind if in the SDKGenerator, I replace :
// In general the version consists of the content of the version element
with an appended build-number.
            String sdkVersion = version + "." + build;
by:
// In general the version consists of the content of the version element
with an appended build-number.
            String sdkVersion = (build.equals("0")) ? version + "-SNAPSHOT"
: version + "." + build;

The build number will be set to 0 only if I do a temporary release from the
sources, never in official releases.

-Fred

-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Thursday, January 31, 2013 10:36 AM
To: dev@flex.apache.org
Subject: AW: AW: Splitting up Flex and Air?

Hi Frederic,

well as far as I know, as long as you use the Air version that was naturally
bundled with the corresponding FDK, then all should work already. The only
problem is that if you want to use a different Air SDK. Currently the adt of
the original FDK is used, but it should be the version shipped with the
desired Air SDK version. That's what I'm intending on doing. The only change
you should need to use that updated version with FM would be that you need
to add a "compiler" artifact for the Flex-SDK as well as one additional
Air-SDK compiler artifact.

Chris


-----Urspr�ngliche Nachricht-----
Von: Fr�d�ric THOMAS [mailto:webdoublefx@hotmail.com]
Gesendet: Donnerstag, 31. Januar 2013 10:28
An: dev@flex.apache.org
Betreff: Re: AW: Splitting up Flex and Air?

Hi Chris,

I'm doing an AIR App, so let me know when you update FM pls, like that I can
test it, btw, do you mind if I update the mavenizer as when the Flex build
number is 0, instead of having a version number + '.0', I put version number
+ "-SNAPSHOT" ?

-Fred

-----Message d'origine-----
From: christofer.dutz@c-ware.de
Sent: Thursday, January 31, 2013 8:44 AM
To: dev@flex.apache.org
Subject: AW: Splitting up Flex and Air?

Hi Om,

Well I think this would definitely be a cool thing. Then the user will have
several ways of getting a mavenized FDK (Intaller, Manually Mavenizing,
Mavenizer integrated into the maven-flex-plugin and by using the
auto-download-feature of the maven-flex-plugin (the one I was talking to
Alex about)).

But before officially adding this, I'd like to modify the mavenizer to
correctly mavenize the Air compiler artifacts (adt.jar, smaili.jar and
baksmali.jar)

Chris


-----Urspr�ngliche Nachricht-----
Von: omuppi1@gmail.com [mailto:omuppi1@gmail.com] Im Auftrag von Om
Gesendet: Donnerstag, 31. Januar 2013 02:35
An: dev@flex.apache.org
Betreff: Re: Splitting up Flex and Air?

Chris, I meant to reply earlier, but forgot.

The installer already downloads everything while displaying the required
licenses along the way.  Do you think having a "Mavenize" button at the end
would be a good idea?  We could just call your mavenize ant script from the
AIR app.  Please let me know if this is something you would be interested.
I would be glad to help you out with this.

Thanks,
Om

On Mon, Jan 28, 2013 at 9:20 AM, christofer.dutz@c-ware.de <
christofer.dutz@c-ware.de> wrote:

> Hey ... I was never talking about distributing them ... The mavenizer
> is all about you downloading (after Accepting whatever license Adobe
> wants you to accept). And then simply to transform this download on
> your local machine. So every user that wants to use it has to mavenize
> a FDK before using it.
>
> The tool I promised to create (as soon as I have the time to do so)
> will take care of the downloading but at this point the Mavenizer
> expects you to download the stuff manually and this code will be the
> base for the tool I am intending on building ... but I don't want to
> go into a discussion about this again.
>
> Currently I'll simply stick to mavenizing every jar in the Air SDK
> into the groupId "com.adobe.air.compiler" and hard-code an exception
> to omit the
> 3 files from "com.adobe.flex.compiler" or "org.apache.flex.compiler".
> I think this should do the trick.
>
> Chris
>
> -----Urspr�ngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Montag, 28. Januar 2013 18:02
> An: dev@flex.apache.org
> Betreff: Re: Splitting up Flex and Air?
>
>
>
>
> On 1/28/13 12:25 AM, "christofer.dutz@c-ware.de" <
> christofer.dutz@c-ware.de>
> wrote:
>
> > Hi,
> >
> > a while ago a user complained that in my Mavenizer I was deploying
> > the Air jars in {fdk-root}/lib to the group
> > org.apache.flex.compiler/com.adobe.flex.compiler ... ths is indeed
> > not quite correct and I would like to fix this.
> >
> > All Air sdks except 2.6 contain only adt.jar so I think I'm on the
> > safe side, but 2.6 has more libs "baksmali.jar", "smali.jar". So
> > would it be safe to hard-code these three jars and to place them in
> > "com.adobe.air.compiler", or would this have negative side-effects?
> >
> I don't know what those jars do.  If they come from the Adobe AIR SDK
> download then unless you have a redistribution agreement with Adobe,
> it is technically not allowed for these jars to be in FlexMojos
> distribution.
>
> That's why in the Apache Flex Maven utilities you promised to write
> that download utility that requires the user accept the license and
> then get the stuff from Adobe.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>