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]> > 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/
