Hi Frederic, Ok ... thanks for reporting this.
I had to force the addition of that pom as git complained, that it was excluded because of one of the active ".gitignore" files rules (I couldn't find the rule that was causing the exclusion). Well after forcing it in I could confirm it's presence by going to the Github web interface. Give it another try ... should work now. Chris ________________________________________ Von: Frédéric THOMAS <webdoubl...@hotmail.com> Gesendet: Donnerstag, 9. April 2015 22:38 An: dev@flex.apache.org Betreff: RE: [MAVENIZER] New dev-version available for playing around with Command Line Interface :-) Hi Chris, I need to re-install my artifactory on my machine, in between, can you check the pom.xml for the CLI has been committed to develop as I can't see it. Thanks, Frédéric THOMAS > From: christofer.d...@c-ware.de > To: dev@flex.apache.org > Subject: [MAVENIZER] New dev-version available for playing around with > Command Line Interface :-) > Date: Wed, 8 Apr 2015 14:30:41 +0000 > > 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 > >
