It might be better to deploy from the flex version of the air sdk. The installer uses the url in the sdk installer config file. Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Christofer Dutz <christofer.d...@c-ware.de> wrote: So is it safe for me just to deploy one jar and ignore the rest? Gesendet mit meinem HTC ----- Reply message ----- Von: "Alex Harui" <aha...@adobe.com> An: "dev@flex.apache.org" <dev@flex.apache.org> Betreff: Why does AIR contain flex libs starting from version 4.0 Datum: So., Mai 11, 2014 16:26 Somewhere around the late 3.x AIR SDKs, they started bundling ASC2.0. But they also provided links to AIR SDKs without ASC2.0 for Flex. The list of links is in our README or RELEASE_NOTES. -Alex On 5/7/14 12:42 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi, > >I'm just spending some more time in the AIR mavenizer and have discoverd >that AIR used to consist of max 3 libs up to 4.0 but starting with 4.0 it >seems to conatin a lot of stuff oft he Flex SDK (compc.jar, mxmlc.jar, >...) Why is this so? I also noticed that all others seem to contain only >adt.jar except 2.6 which contains smali.jar and baksmali.jar which seem >to have been introduced in 2.6 but have been moved to android/lib after >2.6. > >So would it be safe to assume that the "compiler" artifact for AIR only >consists of "adt.jar"? And if I were to deploy smali.jar and baksmali.jar >I should make an exception for 2.6 and deploy them under >"com.adobe.air.compiler.android"? What do I need those two libs for >anyway? As far as I could read it's an Android dalvic >assembler/deassembler. > >Chris
