Well digging even deeper into this I'll probably name it "package-air" goal and pass in the platform type somehow.
It seems Velo initially intended on setting the packaging type of the maven project to configure the output. At least the dead code in Flexmojos suggests this. The class FlexExtension contains all of the constants understood by the adt tool. I don't want to do this as I would like to have an "air" package type which automatically creates the "air" artifact, but allow multiple packaging executions to produce different output bundles in one build ... so I could produce ".air", ".apk", ".ipk", ".exe" and ".dmg" in one run of "mvn package". Currently I'm trying to finish a poc that remote controlls the ADT class. Keep your fingers crossed :-) Chris ________________________________________ Von: piotrz <piotrzarzyck...@gmail.com> Gesendet: Mittwoch, 15. Juli 2015 11:05 An: dev@flex.apache.org Betreff: Re: AW: Thoughts on mobile packaging for Flexmojos Hi Chris, For newbie guys it will be more descriptive if you use Android, iOS. :) Thanks, Piotr ----- Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Thoughts-on-mobile-packaging-for-Flexmojos-tp48508p48512.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
