Ok ... sorry for that ... I completely rewrote the Mavenizer but forgot to rewrite the Readme. Will do that as soon as possible.
Chris ________________________________________ Von: omup...@gmail.com <omup...@gmail.com> im Auftrag von OmPrakash Muppirala <bigosma...@gmail.com> Gesendet: Samstag, 20. September 2014 01:07 An: dev@flex.apache.org Betreff: Re: Flexmojox 7.1.0-SNAPSHOT with included Mavenizer functionality :-) I am trying to follow the steps here [1] When I run 'mvn package' in the flex-utilities/mavenizer directory, everything seems to work fine, but there is no jar file called flex-sdk-converter-1.0.jar in the mavenizer/target directory as mentioned in the README. Thanks, Om [1] https://github.com/apache/flex-utilities/blob/develop/mavenizer/README.txt On Fri, Sep 19, 2014 at 3:07 PM, OmPrakash Muppirala <bigosma...@gmail.com> wrote: > Chris, > > To test this, are these the correct steps? > > > 1. Get the Mavenizer from here [1], follow instructions in README. > 2. Copy over the generated Flex SDK artifacts to the local .m2 > directory > 3. In my project's pom.xml, > - update flexmojos.version to to 7.1.0 > - update flex.sdk.version to 4.13.0 > - update flashplayer.version.major to 14 > 4. Run mvn as usual and accept the Adobe license question when it pops > up. > > Am I missing something? > > Thanks, > Om > > [1] https://github.com/apache/flex-utilities/tree/develop/mavenizer > > On Fri, Sep 19, 2014 at 1:34 PM, Christofer Dutz < > christofer.d...@c-ware.de> wrote: > >> ?Hi Guys, >> >> >> I just wanted to inform you that the latest SNAPSHOT version of Flexmojos >> 7.1.0 will utilize the 1.0.0-SNAPSHOT version of the Apache Flex Mavenizer. >> >> >> While my changes from today will have no effect on existing Flexmojos >> builds , it now allows to omit the playerglobal or airglobal dependencies. >> When omiting the runtime artifacts it is however necessary to specify the >> 'flashVersion' or 'airVersion' config parameter in order to tell flexmojos >> which artifacts to use. Flexmojos will automatically add missing >> dependencies. If these are resolveable locally or from a remote repository >> nothing special will happen. If however you specify a runtime version that >> is not available locally or remotely, the Maveizer will display the "Adobe >> license Agreement acceptance question". If and only if you type "yes" and >> hit enter will it automatically download the missing artifact and >> automatically mavenize it. After this the build continues as usual. The >> next time the build will find the artifact in the local repository and not >> download it again. ?In companies it is now up to the admins to deploy these >> artifacty in the company repositories. If this is done, noone else and >> especially no CI build will have to deal with anything special. >> >> >> I would like to invite you to use and test this feature. As soon as it >> seems to be working for a set of users without any problems, I would like >> to release the Mavenizer as this is a requirement to releasing the next >> Flexmojos version. >> >> >> One thing I did notice, was that on a mac the extraction of an Air SDK >> seems to take for ages. I remember the same functionality being a lot >> faster on a Windows machine. Probably its a lot faster to extract a zip >> than a tbz archive. Eventually we have to change the way tbz archives are >> extracted. >> >> >> If you were setting the 'playerVersion' configuration option. You need to >> rename this to 'flashVersion'. Setting of 'flashVersion' will result in >> 'playerVersion' being set to the value of 'flashVersion' on the compiler >> output. I needed to do this so make the configuration options slightly more >> intuitive. I didn't like the idea of setting "airVersion" or >> "playerVersion". >> >> >> You would make me really happy if I got some responses on this ... >> without any feedback it's hard to find any problems. So please, you >> flexmojos out here ... give the feature a short spin with a project or two. >> >> >> Chris >> >> >> >> >
