Chris,
Thanks for your time and hard work:
So, like mentioned, in one attempt I did manage to successfully mavenize
Flex4.6 and AIR3.5, so the mavenized target directory includes:
com
> adobe
> air
> flash
> flex
Questions:
1. How do I specify in a pom.xml to use Flex 4.6 AND AIR 3.5? For Flex, it
looks like it's basically the same as before:
<dependency>
<groupId>com.adobe.flex</groupId>
<artifactId>compiler</artifactId>
<version>4.6.0.23201</version>
<type>pom</type>
</dependency>
... BUT specifying the AIR sdk version seems somewhat more confusing... How
do I specify using AIR 3.5? There's no adt in the mavenized adobe.com.air
package(s), so, I'm assuming that we're still reliant on the adt at
com.adobe.flex.compiler? It feels sort of weird to have to do:
<dependency>
<groupId>com.adobe.flex.compiler</groupId>
<artifactId>adt</artifactId>
<version>4.6.0.23201</version>
</dependency>
Just wondering, because a lot of AIR only development is now occurring, so,
accessing the adt via a Flex artifacts seems sort of confusing...
And to specify the AIR 3.5 framework?
<dependency>
<groupId>com.adobe.air.framework</groupId>
*<artifactId>air-framework</artifactId>*
<version>3.5</version>
<type>pom</type>
</dependency>
Previously, the artifact id would be "air-framework", but that artifact id
doesn't exist in your target output in the com.adobe.air.framework package.
Should the artifact id be aircore, airglobal or common-framework? My
guess would be the latter...
*
*
*Would it be possible for you to provide a pom.xml example using Flexmojos6
and a mavenized version of Flex and AIR? * That would probably shed a lot
of light on this process and I'd greatly appreciate it!
Technically speaking, before mavenizing, if we previously overwrote the AIR
files in the Flex SDK directory with AIR 3.5 files (the old school way of
preparing a Flex SDK with the desired version of the AIR SDK), and then
mavenzied the Flex SDK, we should be able to use just the artifacts in the
com.adobe.flex.framework packages, no? These would now point to all things
AIR 3.5, no? Would this not even work with Flexmojos 4x?
Man, thanks for your time!
I'd be happy to get more involved, so feel free to contact me about further
discussions. Thanks!
On Thursday, December 27, 2012 4:08:12 AM UTC-5, Christofer Dutz wrote:
>
> Air and Flashplayer were historically bundled with each FDK. While the
> Flashplayer only was a few files the complete AIR SDK directory way mixed
> into the FDK directories. The Mavenizer knows which artifacts are Flex, Air
> and Flash and separates them.
>
> Flex: com.adobe.flex / org.apache.flex
> Flash: com.adobe.flash
> Air: com.adobe.air
>
> So as soon as you deploy an Adobe Flex SDK you also deploy the Flashplayer
> and the Air SDK. With Apache Flex this will not be possible as Apache
> doesn't have the rights to bundle these. In this case you can manually
> bundle the Air SDK and reference this.
>
> One part of the confusion might be that in Velos FDK there were a lot of
> "playerglobal-11.1-4.5.1.12213" (flash and air artifacts were bundled
> inside the flex framework and all of them were re-distributed for any new
> fdk. I took the opportunity to re-structure everything and separate
> flashplayer and air form flex. Now you can specify flex, flash and air
> version separately.
>
> The resulting directory stucture is intended to be directly copied to
> ".m2/repository" directory. In this case you don't need the Deployer.
> Simply copy the generated Maven stuff into you local maven repo.
>
>
> Chris
>
>
>
> 2012/12/21 Asking Dumbquestions <[email protected] <javascript:>>
>
>> 2. AIR 3.5 requires the playerglobal 11.5. The AIR 3.5 SDK source that I
>> used to Mavenize included the required 11.5 player at
>> "air3.5/frameworks/libs/player/11.5", however, I don't find this player in
>> the Mavenized version, but I do see the player 11.1 (probably from AIR
>> 3.1). Will this be an issue?
>>
>
>
--
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos
http://flexmojos.sonatype.org/
