You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Frédéric THOMAS <we...@hotmail.com> on 2015/04/08 20:00:46 UTC
Re : [MAVENIZER] New dev-version available for playing around with Command Line Interface :-)
Will try that tomorrow, I like this new way.
--- Message initial ---
De : "Christofer Dutz" <ch...@c-ware.de>
Envoyé : 8 avril 2015 15:31
A : dev@flex.apache.org
Objet : [MAVENIZER] New dev-version available for playing around with Command Line Interface :-)
Hi,
while I was at it to implement the last changes I saw for the first release, I also removed all the old legacy "main" classes and replaced them with one Commandline Interface (module cli)
If you checkout the "develop" branch of the flex-utils repo, and build the Mavenizer using "mvn clean install", you will get a "cli/target/apache-flex-sdk-converter-1.0.0-SNAPSHOT.jar"
in the "cli/target" directory run the cli like this:
java -jar apache-flex-sdk-converter-1.0.0-SNAPSHOT.jar ... (followed by the commands you want it to execute)
Currently there are 4 commands:
list: Lists all versions and platforms available for download
download: Downloads selected versions and assembles an FDK
convert: Converts a previously installed (using the installer) or assembled (using download command) FDK into a mavenized form.
deploy: Uploads previously created maven artifacts to a remote repository.
Some typical usage scenarios:
- Create a mavenized version of a previously installed FDK (Using the installer):
"... -fdkDir <FDK install dir> -mavenDir <maven local repo> convert"
- Download and create an FDK (Flex 1.4.1 with playerglobal 17.0 and 16.0 AIR SDK 17.0 for Windows and Mac and the fontkit libs):
"... -fdkDir <FDK target dir> -flexVersion 4.14.1 -flashVersion 17.0,16.0 -airVersion 17.0 -platform WINDOWS,MAC -fontkit download"
- Download and convert an FDK (FDK assembled in temp directory using Air for current systems platform only):
"... -flexVersion 4.14.1 -flashVersion 17.0 -airVersion 17.0 -fontkit -mavenDir <maven local repo> download convert"
- Deploy a bunch of maven artifacts to a remote maven repository:
"... -mavenDir <dir with maven artifacts> -repoUrl <url> -repoUsername <username> -repoPassword <pasword> deploy"
- "The works" (TM): Download, Convert and Deploy using only temp directories:
"... -flexVersion 4.14.1 -flashVersion 17.0 -airVersion 17.0 -fontkit -repoUrl <url> -repoUsername <username> -repoPassword <pasword> download convert deploy"
Would be cool if you guys could experiment a little with it ... I think it could probably need a little hardening here and there. The more experiment with it, the harder it gets :-)
Chris
AW: Re : [MAVENIZER] New dev-version available for playing around with Command Line Interface :-)
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok ... so I tried one of my largest projects with a FDK 4.14.1 with the artifacts produced by the new Mavenizer.
Due to the fact that now the compiler no longer contains the fontkit libraries my build fails (as expected) as soon as I do font encoding stuff. If you need to do font encoding, just add the following plugin-dependency to your plugin configuration:
<dependency>
<groupId>com.adobe</groupId>
<artifactId>fontkit</artifactId>
<version>1.0</version>
</dependency>
And your build should work again.
I only needed to add this to my skin module, which was the only one doing font encoding stuff.
Unfortunately I noticed a problem with the threadlocaltoolkit in Flaxmojos 7.1.0-SNAPSHOT ... something with the mavenResolvers must have changed ... will look into this, but all compiled fine with FM 7.0.1 and the Threadloacaltoolkit problem is not related to my new maven structure.
Chris
________________________________________
Von: Frédéric THOMAS <we...@hotmail.com>
Gesendet: Mittwoch, 8. April 2015 20:00
An: dev@flex.apache.org
Betreff: Re : [MAVENIZER] New dev-version available for playing around with Command Line Interface :-)
Will try that tomorrow, I like this new way.
--- Message initial ---
De : "Christofer Dutz" <ch...@c-ware.de>
Envoyé : 8 avril 2015 15:31
A : dev@flex.apache.org
Objet : [MAVENIZER] New dev-version available for playing around with Command Line Interface :-)
Hi,
while I was at it to implement the last changes I saw for the first release, I also removed all the old legacy "main" classes and replaced them with one Commandline Interface (module cli)
If you checkout the "develop" branch of the flex-utils repo, and build the Mavenizer using "mvn clean install", you will get a "cli/target/apache-flex-sdk-converter-1.0.0-SNAPSHOT.jar"
in the "cli/target" directory run the cli like this:
java -jar apache-flex-sdk-converter-1.0.0-SNAPSHOT.jar ... (followed by the commands you want it to execute)
Currently there are 4 commands:
list: Lists all versions and platforms available for download
download: Downloads selected versions and assembles an FDK
convert: Converts a previously installed (using the installer) or assembled (using download command) FDK into a mavenized form.
deploy: Uploads previously created maven artifacts to a remote repository.
Some typical usage scenarios:
- Create a mavenized version of a previously installed FDK (Using the installer):
"... -fdkDir <FDK install dir> -mavenDir <maven local repo> convert"
- Download and create an FDK (Flex 1.4.1 with playerglobal 17.0 and 16.0 AIR SDK 17.0 for Windows and Mac and the fontkit libs):
"... -fdkDir <FDK target dir> -flexVersion 4.14.1 -flashVersion 17.0,16.0 -airVersion 17.0 -platform WINDOWS,MAC -fontkit download"
- Download and convert an FDK (FDK assembled in temp directory using Air for current systems platform only):
"... -flexVersion 4.14.1 -flashVersion 17.0 -airVersion 17.0 -fontkit -mavenDir <maven local repo> download convert"
- Deploy a bunch of maven artifacts to a remote maven repository:
"... -mavenDir <dir with maven artifacts> -repoUrl <url> -repoUsername <username> -repoPassword <pasword> deploy"
- "The works" (TM): Download, Convert and Deploy using only temp directories:
"... -flexVersion 4.14.1 -flashVersion 17.0 -airVersion 17.0 -fontkit -repoUrl <url> -repoUsername <username> -repoPassword <pasword> download convert deploy"
Would be cool if you guys could experiment a little with it ... I think it could probably need a little hardening here and there. The more experiment with it, the harder it gets :-)
Chris