I'm pretty sure the 'mavenize' button will bring a huge smile to a lot of developers out there. So, once Christofer finishes his last changes I think this would be a really excellent addition to the installer. +1 from me :)
On 31 January 2013 08:44, christofer.d...@c-ware.de < christofer.d...@c-ware.de> wrote: > Hi Om, > > Well I think this would definitely be a cool thing. Then the user will > have several ways of getting a mavenized FDK (Intaller, Manually > Mavenizing, Mavenizer integrated into the maven-flex-plugin and by using > the auto-download-feature of the maven-flex-plugin (the one I was talking > to Alex about)). > > But before officially adding this, I'd like to modify the mavenizer to > correctly mavenize the Air compiler artifacts (adt.jar, smaili.jar and > baksmali.jar) > > Chris > > > -----Ursprüngliche Nachricht----- > Von: omup...@gmail.com [mailto:omup...@gmail.com] Im Auftrag von Om > Gesendet: Donnerstag, 31. Januar 2013 02:35 > An: dev@flex.apache.org > Betreff: Re: Splitting up Flex and Air? > > Chris, I meant to reply earlier, but forgot. > > The installer already downloads everything while displaying the required > licenses along the way. Do you think having a "Mavenize" button at the end > would be a good idea? We could just call your mavenize ant script from the > AIR app. Please let me know if this is something you would be interested. > I would be glad to help you out with this. > > Thanks, > Om > > On Mon, Jan 28, 2013 at 9:20 AM, christofer.d...@c-ware.de < > christofer.d...@c-ware.de> wrote: > > > Hey ... I was never talking about distributing them ... The mavenizer > > is all about you downloading (after Accepting whatever license Adobe > > wants you to accept). And then simply to transform this download on > > your local machine. So every user that wants to use it has to mavenize > > a FDK before using it. > > > > The tool I promised to create (as soon as I have the time to do so) > > will take care of the downloading but at this point the Mavenizer > > expects you to download the stuff manually and this code will be the > > base for the tool I am intending on building ... but I don't want to > > go into a discussion about this again. > > > > Currently I'll simply stick to mavenizing every jar in the Air SDK > > into the groupId "com.adobe.air.compiler" and hard-code an exception > > to omit the > > 3 files from "com.adobe.flex.compiler" or "org.apache.flex.compiler". > > I think this should do the trick. > > > > Chris > > > > -----Ursprüngliche Nachricht----- > > Von: Alex Harui [mailto:aha...@adobe.com] > > Gesendet: Montag, 28. Januar 2013 18:02 > > An: dev@flex.apache.org > > Betreff: Re: Splitting up Flex and Air? > > > > > > > > > > On 1/28/13 12:25 AM, "christofer.d...@c-ware.de" < > > christofer.d...@c-ware.de> > > wrote: > > > > > Hi, > > > > > > a while ago a user complained that in my Mavenizer I was deploying > > > the Air jars in {fdk-root}/lib to the group > > > org.apache.flex.compiler/com.adobe.flex.compiler ... ths is indeed > > > not quite correct and I would like to fix this. > > > > > > All Air sdks except 2.6 contain only adt.jar so I think I'm on the > > > safe side, but 2.6 has more libs "baksmali.jar", "smali.jar". So > > > would it be safe to hard-code these three jars and to place them in > > > "com.adobe.air.compiler", or would this have negative side-effects? > > > > > I don't know what those jars do. If they come from the Adobe AIR SDK > > download then unless you have a redistribution agreement with Adobe, > > it is technically not allowed for these jars to be in FlexMojos > distribution. > > > > That's why in the Apache Flex Maven utilities you promised to write > > that download utility that requires the user accept the license and > > then get the stuff from Adobe. > > > > -- > > Alex Harui > > Flex SDK Team > > Adobe Systems, Inc. > > http://blogs.adobe.com/aharui > > > > > -- regards, Roland -- Roland Zwaga Senior Consultant | Stack & Heap BVBA +32 (0)486 16 12 62 | rol...@stackandheap.com | http://www.stackandheap.com http://zwaga.blogspot.com http://www.springactionscript.org http://www.as3commons.org
