I'm not a Maven user, so maybe I'm unclear what the main use cases are. One
of the ones that I was told about was quickly updating to new versions of
Flex, and I assumed it might also mean updating to new versions of the
player or AIR SDK.

Switching SDK, is as easy as changing a property in only one pom.xml, nothing else to do as soon as the SDK you want to use is mavenized obviously, the player itself is not needed, we can specify the target version but there's no dependencies. During the SDK mavenization process (with the mavenizer), a relation between Flex SDK and Air SDK is etablished, it's done by comparing the checksum of the airglobal.swc inside each Air SDKs and the ones inside each Flex SDKs.

but when building a .AIR file (and or an AIRI for signing) or a mobile package,
I'm pretty sure other parts of the AIR SDK are involved and that they might
change between AIR versions.

AFAIK, airglobal.swc and ADT only are needed for packaging into AIR, AIRI, ANE, EXE, APK, IPA, ..., at the moment FlexMojos uses a class of the adt.jar called AIRPackager and call the createAIR method instead of using the ADT class, therefore it can package only into AIR (which is already something appreciated).

Not sure I anwsered at everything you want, only the things I understood you want, ask again please for more precisions.

- Fred.

-----Message d'origine----- From: Alex Harui
Sent: Saturday, November 24, 2012 11:55 PM
To: flex-dev@incubator.apache.org
Subject: Re: Who's a flex compiler-configuration pro on this list?

I'm not a Maven user, so maybe I'm unclear what the main use cases are.  One
of the ones that I was told about was quickly updating to new versions of
Flex, and I assumed it might also mean updating to new versions of the
player or AIR SDK.

I can see dropping in new versions of playerglobal.swc or airglobal.swc, but
when building a .AIR file (and or an AIRI for signing) or a mobile package,
I'm pretty sure other parts of the AIR SDK are involved and that they might
change between AIR versions.

Or can you install an AIR SDK once and change airglobal versions and it will
all work?

-Alex


On 11/24/12 4:05 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:

Hi,

@Alex, not sure actually about what you mean by "cover release packaging of
AIR apps" but with flexmojos I can compile and package into AIR which once
installed run an .exe, all it needs is airglobal.swc and adt.jar.

See
https://svn.apache.org/repos/asf/incubator/flex/whiteboard/fthomas/developerTo
olSuite/trunk/

If I missed something, please let me know.

- Fred.

-----Message d'origine-----
From: Alex Harui
Sent: Friday, November 23, 2012 9:53 PM
To: flex-dev@incubator.apache.org
Subject: Re: AW: AW: Who's a flex compiler-configuration pro on this list?

OK, let's wait until next week and see if others agree that just having
different versions of airglobal.swc available from Adobe would be
sufficient. It is all you may need to compile a simple swf, but to produce
final release packages, I think there are other pieces of the AIR SDK that
you need. Maybe the FlexMojos testsuite doesn't cover release packaging of
AIR apps?


On 11/23/12 4:45 AM, "christofer.d...@c-ware.de" <christofer.d...@c-ware.de>
wrote:

Well my Mavenizer doesn't deploy any air stuff besides the airglobal.swc
and
in the Flexmojos Testsuite there are tests for the different Air features
and
I am not having any trouble with that.
The only thing is that I do have to provide the same third party libs the
Flex
SDK needs to have provided. So if you are talking about these libs, you
might
be correct.
But It would already be a great improvement to be able to build Flex
applications without manual intervention.
I have to admit that I have never ever done any Air yet nor any of the
Flex
guys around here that I have worked with.

Don't get me wrong. I'm not claiming that Nobody uses Air ... it's just
that
for those not using it this would be a great improvement.

Chris

-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aha...@adobe.com]
Gesendet: Donnerstag, 22. November 2012 17:26
An: flex-dev@incubator.apache.org
Betreff: Re: AW: Who's a flex compiler-configuration pro on this list?




On 11/21/12 11:59 PM, "christofer.d...@c-ware.de"
<christofer.d...@c-ware.de> wrote:

Buuuuuut ... thinking of it :-)

Mabe it would indeed be better to start with Falcon as this is
definitely the future of Flex and Flexmojos already lets you build
using MXMLC ... And I always wanted to start digging into it, but
never actually found a usecase for it.

@Alex: Perhaps if Adobe were to publish the playerglobal and the
airglobal (Don't need the runtime ... think mavenizing the Runtim is
too much ... would simply use the runtimes from PATH).
Without those TWO artifacts the final solution would always be
half-baked (No matter what compiler) as no user could: "simply add the
plugin and start coding flex" :-) So what do you think? You make the
one thing happen, and I'll do the second?
;-)

I need convincing that this will work for captive runtime for mobile apps,
and
not sure how you are supposed to get the other executables that help make
up
the AIR package.

But if you want to try prototyping it, feel free.  I wll try to find time
to
help next week, if you need help. I want to make sure it will work before
we
go ask for approvals.

--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Reply via email to