I assume you have seen this?

http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac35eb7b4e12cddc5fbbb-8000.html

Thanks,
Om
On Jul 18, 2015 11:08 AM, "Christofer Dutz" <christofer.d...@c-ware.de>
wrote:

> Anyone here could send me a command line that actually creates a valid iOS
> application?
> If I use IntelliJ to compile my flexmojos application I get an about 9.8MB
> big file that runs on my iPhone. If I use flexmojos currently the output is
> about 1.1MB big and it doesn't run. So something must be different ...
> unfortunately I don't seem to be able to have IntelliJ output what it's
> doing :-(
>
> So if you could send me the command line for generating a valid ios
> application, it would make things a lot easier for me.
>
> Chris
>
> ________________________________________
> Von: carlos.rov...@gmail.com <carlos.rov...@gmail.com> im Auftrag von
> Carlos Rovira <carlos.rov...@codeoscopic.com>
> Gesendet: Samstag, 18. Juli 2015 18:59
> An: dev@flex.apache.org
> Betreff: Re: Finally ... Mobile Packaging in Flexmojos (Was: AW: AW:
> Thoughts on mobile packaging for Flexmojos)
>
> Awesome Chris!
> This was an importance feature that was needed to complete maven flex
> support. :D
>
>
> 2015-07-18 15:10 GMT+02:00 Christofer Dutz <christofer.d...@c-ware.de>:
>
> > Ok ... so have a look at this listing of my projects target directory :-)
> >
> > drwxr-xr-x   5 christoferdutz  staff       170 18 Jul 15:00 adt
> > drwxr-xr-x  21 christoferdutz  staff       714 18 Jul 15:00 classes
> > -rw-r--r--   1 christoferdutz  staff  14604776 18 Jul 15:01
> > dukecon-flex-core-1.0.0-SNAPSHOT-captive.apk
> > -rw-r--r--   1 christoferdutz  staff     40034 18 Jul 15:00
> > dukecon-flex-core-1.0.0-SNAPSHOT-configs.xml
> > -rw-r--r--   1 christoferdutz  staff     12771 18 Jul 15:00
> > dukecon-flex-core-1.0.0-SNAPSHOT-descriptor.xml
> > -rw-r--r--   1 christoferdutz  staff    881388 18 Jul 15:00
> > dukecon-flex-core-1.0.0-SNAPSHOT-link-report.xml
> > -rw-r--r--   1 christoferdutz  staff    176520 18 Jul 15:00
> > dukecon-flex-core-1.0.0-SNAPSHOT-size-report.xml
> > -rw-r--r--   1 christoferdutz  staff   3416552 18 Jul 15:00
> > dukecon-flex-core-1.0.0-SNAPSHOT.apk
> > -rw-r--r--@  1 christoferdutz  staff   3518470 18 Jul 15:00
> > dukecon-flex-core-1.0.0-SNAPSHOT.dmg
> > -rw-r--r--@  1 christoferdutz  staff   3518637 18 Jul 15:00
> > dukecon-flex-core-1.0.0-SNAPSHOT.exe
> > -rw-r--r--@  1 christoferdutz  staff   3518561 18 Jul 15:00
> > dukecon-flex-core-1.0.0-SNAPSHOT.rpm
> > -rw-r--r--   1 christoferdutz  staff   3352373 18 Jul 15:00
> > dukecon-flex-core-1.0.0-SNAPSHOT.swf
> > -rw-r--r--   1 christoferdutz  staff      6289 18 Jul 15:00 fonts.ser
> > drwxr-xr-x   3 christoferdutz  staff       102 18 Jul 15:00
> > generated-sources
> > drwxr-xr-x   2 christoferdutz  staff        68 18 Jul 15:00
> > surefire-reports
> > drwxr-xr-x   2 christoferdutz  staff        68 18 Jul 15:00 test-classes
> >
> > So we have Android, Android-Captive, Windows, Mac and Linux generally up
> > and running ... Have to find out how to make the Desktop variants include
> > the captive runtime though (And yes ... definitely Linux will not work
> with
> > Air 18.0)
> >
> > As soon as that's done I'll try to get iOS packaging running. And as soon
> > as that's done I'll publish a new SNAPSHOT of Flexmojos (7.1.0-SNAPSHOT)
> >
> > Chris
> >
> >
> > ________________________________________
> > Von: Christofer Dutz <christofer.d...@c-ware.de>
> > Gesendet: Freitag, 17. Juli 2015 15:37
> > An: dev@flex.apache.org
> > Betreff: AW: AW: Thoughts on mobile packaging for Flexmojos
> >
> > Ok ... after getting the air and apk with shared runtime packaging
> > working, I started working on the apks with captive runtimes. Adobe sort
> of
> > hard-coded where adt looks for stuff while with shared runtimes. This
> isn't
> > too bad cause all stuff it's looking for is relative and below to the
> > location of adt.jar. As soon as it comes to captive runtimes the path
> seems
> > to be: ../runtimes/air and ../runtimes/air-captive ... this is really bad
> > for using this in maven as multiple versions of adt would share one
> > runtimes directory and I would start polluting my maven lokal repo with
> > non-maven-nonsense.
> >
> > Therefore I started a completely new approach. I created several
> packagers
> > that know what they need to operate. In a setup-phase such a packager
> > retrieves maven artifacts and installs a minimal AIR sdk in the
> target/adt
> > directory of the current project. This contains all the parts it needs to
> > do its job, but only those parts. So for air only adt.jar is needed, for
> > android all the android stuff is added too ... I hope this will keep the
> > overhead to a minimum.
> >
> > As soon as the mini sdks are prepared I have to start a new JVM which I
> > pass in the parameters the same way I would when executing adt commands
> on
> > the command line.
> >
> > For this I had to throw away EVERYTHING of the old sign-air mojo of
> > Flexmojos. I started from scratch and am extending the thing with
> > parameters as needed. The cool thing is that from now on IntelliJ will
> > never ever again complain about this stupid "storepass" as the sign-air
> > mojo was the one requesting this.
> >
> > For me it would be interesting which config options you guys need as I
> > will be adding them on a need to build basis.
> >
> > At least now "air", "apk" and "apk-captive-runtime" seem to be working
> ...
> > at least I can install all on my Mac (air, android) and the apk
> (android),
> > apk-captive-runtime (android)
> >
> > Chris
> >
> > ________________________________________
> > Von: Christofer Dutz <christofer.d...@c-ware.de>
> > Gesendet: Donnerstag, 16. Juli 2015 10:48
> > An: dev@flex.apache.org
> > Betreff: AW: AW: Thoughts on mobile packaging for Flexmojos
> >
> > Ok ... more good news ...
> >
> > I just updated the mavenizer to package the missing parts.
> >
> > Together with my lokal changes on Flexmojos I am now able do do native
> > packaging for Android without any need to do tweaking ... but now I'll
> have
> > to concentrate on correct parametrization of the Air packagers. Currently
> > my Android application is bundled as APK file, but the name is still
> ".air"
> > and even if the log output claims it to contain the native runtime, it
> > seems not to contain it ... will take a little, but I think at last we
> are
> > on the finishing track. As soon as I'm happy with Android, I'll probably
> > work on Desktop (Windows, Mac, ...) ... after that the iOS support will
> > probably suck most ;-)
> >
> > Will have to do some testing on windows machines as I'm currently only
> > working on my Mac ... especially regarding iOS packaging this is probably
> > the biggest challenge.
> >
> > Chris
> >
> > ________________________________________
> > Von: Christofer Dutz <christofer.d...@c-ware.de>
> > Gesendet: Mittwoch, 15. Juli 2015 16:27
> > An: dev@flex.apache.org
> > Betreff: AW: AW: Thoughts on mobile packaging for Flexmojos
> >
> > First things first:
> >
> > [INFO] --- flexmojos-maven-plugin:7.1.0-SNAPSHOT:package-air
> > (default-package-air) @ dukecon-flex-core ---
> > [INFO] Flexmojos 7.1.0-SNAPSHOT
> > [INFO]   GPL License - Version 2.0 (NO WARRANTY) - See COPYRIGHT file
> > [INFO]   completed 0 of 100
> > NOTE: The application has been packaged with a shared runtime.
> > [INFO]   completed 100 of 100
> > [INFO]   AIR package created:
> >
> /Users/christoferdutz/Projects/JUG-DA/DukeCon/DukeCon-Flex/core/target/dukecon-flex-core-1.0.0-SNAPSHOT.air
> > [INFO]
> > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @
> > dukecon-flex-core ---
> > [INFO] Installing
> >
> /Users/christoferdutz/Projects/JUG-DA/DukeCon/DukeCon-Flex/core/target/dukecon-flex-core-1.0.0-SNAPSHOT.air
> > to
> >
> /Users/christoferdutz/Maven-Repository/org/dukecon/dukecon-flex-core/1.0.0-SNAPSHOT/dukecon-flex-core-1.0.0-SNAPSHOT.air
> > [INFO] Installing
> > /Users/christoferdutz/Projects/JUG-DA/DukeCon/DukeCon-Flex/core/pom.xml
> to
> >
> /Users/christoferdutz/Maven-Repository/org/dukecon/dukecon-flex-core/1.0.0-SNAPSHOT/dukecon-flex-core-1.0.0-SNAPSHOT.pom
> > [INFO] Installing
> >
> /Users/christoferdutz/Projects/JUG-DA/DukeCon/DukeCon-Flex/core/target/dukecon-flex-core-1.0.0-SNAPSHOT.swf
> > to
> >
> /Users/christoferdutz/Maven-Repository/org/dukecon/dukecon-flex-core/1.0.0-SNAPSHOT/dukecon-flex-core-1.0.0-SNAPSHOT.swf
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD SUCCESS
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 57.582s
> > [INFO] Finished at: Wed Jul 15 15:58:31 CEST 2015
> > [INFO] Final Memory: 29M/232M
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > Even if the file name create seems to be wrong (well it has to be wrong
> as
> > I only changed the packager not the name of the output file), but the
> file
> > output seems to be an APK as I could install it on my android device 8-D
> > (Judging from the size though it doesn't seem to be containing the
> captive
> > runtime ... even if the log seems to be claiming to include it)
> >
> > So the POC was successful ... now I have to think of a way how to get
> this
> > useable. First thing will be an adjustment of the SDK Converter to deploy
> > the (smali and baksmali) in the lib/android/lib directory as part of the
> > air compiler artifact. Then I'll have to zip up everything else in the
> > android directory as a zip and add that as a zip to the adt artifact with
> > the classifier "android". This zip needs to be downloaded and extracted
> as
> > it is required to be located in the same directory as the adt.jar (So
> I'll
> > do it the same way the flex framework-zip is handled)
> >
> > Think it will be a difficult task to get this working properly, but I
> > think with this first POC I have at least proven that it's possible :-)
> >
> > Chris
> >
> >
> > ________________________________________
> > Von: Christofer Dutz <christofer.d...@c-ware.de>
> > Gesendet: Mittwoch, 15. Juli 2015 11:37
> > An: dev@flex.apache.org
> > Betreff: AW: AW: Thoughts on mobile packaging for Flexmojos
> >
> > 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.
>
>
>
>
> --
>
> Carlos Rovira
> Director General
> M: +34 607 22 60 05
> http://www.codeoscopic.com
> http://www.avant2.es
>
>
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
>
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> servicio o información solicitados, teniendo usted derecho de acceso,
> rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
> oficinas c/ Tres Creus, nº 104, 2-1, 08202 de Sabadell (Barcelona) con la
> documentación necesaria.
>

Reply via email to