flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject AW: Mavnizer refactoring ... done :-)
Date Sun, 25 May 2014 09:41:02 GMT
Hi Alex,

I am not concerned about any legal issues, I just wanted to know if I implemented everything
the way Adobe would require me to.
I took the questions resources from the installer and you actively have to type "yes" ...
so I hope this is all I need to do to make Adobe happy :-)


-----Urspr√ľngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com] 
Gesendet: Sonntag, 25. Mai 2014 06:22
An: dev@flex.apache.org
Betreff: Re: Mavnizer refactoring ... done :-)

Congratulations.  I will try to take a look.  What legal issues are you concerned about?


On 5/24/14 12:58 PM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:

>Hi guys,
>I just comitted my changes to the "mavenizer-refactoring" branch. At 
>the moment it seems to contain all the parts I need to continue work on 
>Flexmojos to auto download missing Adobe artifacts.
>The mavenizer is now modular. It consists of several modules for 
>retrieving, converting and deploying sdks. This makes it easier to 
>include only the needed parts in other tools such as Flexmojos. The 
>central part is the "core" module which contains 3 classes:
>-          AirDownloader: Takes 3 Arguments "air-version", "target-dir",
>"platform (WINDOWS, LINUX, MAC)"
>-          FlashDownloader: Takes 2 Arguments "flash-version",
>-          SDKConverter: Takes 2 Arguments "source-dir", "target-dir"
>The first two classes tell you that special licenses apply to them and 
>ask the user to accept them by typing "yes" (case insensitive). After 
>entering "yes" the tool downloads the archive to the temp directory, 
>unpacks its content and runs the mavenizer on this. I would especially 
>like to ask Alex to verify if the output and the confirmation mechanism 
>is enough from Adobes point. If its ok, I'd like to continue making 
>Flexmojos 7.1.0-SNAPSHOT run with the slightly new Maven structure. As 
>soon as that's done, I'll add the new Mojo that automatically downloads 
>and mavenizes Adobe artifacts using AirDownloader and FlashDownloader.
>Would certainly like some feedback on the legal things and what you 
>think of my adjustments to the generated maven artifacts and poms.
>I have to admit that I haven't tried the Deployers yet ... but that 
>will follow.
>One thing that currently isn't possible, is to automatically mavenize a 
>set of FDKs ... currently you have to mavenize one FDK after the other 
>(Which seems to me as the more usual way).

View raw message