Hello Chris, Not sure if it is good idea to ask such often .... but, what are the news? :)
On Fri, May 16, 2014 at 10:11 PM, Maxim Solodovnik <[email protected]> wrote: > Thanks for the update Chris :) > Looking forward to test it :) > > > On Fri, May 16, 2014 at 3:54 AM, Christofer Dutz < > [email protected]> wrote: > >> Hi Maxim, >> >> Well I re-wrote the Mavenizer to mavenize, Air, Flash and Flex seperately >> (developer branch). >> Will have to write some missing glue-code to fetch artifacts from an url >> and mavenize that. >> After that I'll have to make sure Flexmojos runs on those slightly >> different Maven artifacts. >> After that comes the PrepareMojo ... still a while to go ... but I'm >> having some progress. >> >> Chris >> >> >> -----Ursprüngliche Nachricht----- >> Von: Maxim Solodovnik [mailto:[email protected]] >> Gesendet: Donnerstag, 8. Mai 2014 16:26 >> An: [email protected] >> Betreff: Re: AW: flexmojos-maven-plugin: building flex project without >> mavenizing Flex binaries >> >> Hello Christofer! >> >> any news on this? :) >> >> >> On Wed, Apr 30, 2014 at 2:30 PM, Christofer Dutz >> <[email protected]>wrote: >> >> > Well actually Alex and I have discussed that I will be implementing >> > the following solution: >> > >> > We will be deploying Apache Flex without any AIR or Flash artifacts. >> > But we will be gerating some dummy artifacts >> > org.apache.flex.runtime.flash or org.apache.flex.runtime.air in which >> > the user references the desired flash or air runtime version. >> > In the Prepare Mojo I will be cheking if for every >> > org.apache.flex.runtime.flash a matching com.adobe.flash and >> > org.apache.flex.runtime.air a matching com.adobe.air artifact is >> > present in the build. If not, it tries to download the artifact from a >> > remote repository. If this is not possible it outputs some license >> > text and asks the user if he accepts. If he does, it downloads the >> > corresponding binary blob (as defined in the config script of our new >> > installer) and then executes the mavenizer part to create the missing >> > artifacts. Then a dynamic reference to these artifacts is added to the >> > build. >> > >> > This way any user has to accept the Adobe license Agreement and after >> > accepting he can deploy the Adobe artifacts to his companies maven repo. >> > The other team-users (and the ci server) would now be able to >> > automatically download these artifacts from now on without having to >> > ask someone to accept the license. >> > >> > All I all I want to create this functionality in a way that I can >> > easily use that in Flexmojos as well as the new Apache Flex Plugin I >> > started working on a while ago. >> > >> > So far what we have planned. >> > >> > Chris >> > >> > >> > ________________________________________ >> > Von: Simon Morvan <[email protected]> >> > Gesendet: Dienstag, 29. April 2014 21:46 >> > An: [email protected] >> > Betreff: Re: AW: flexmojos-maven-plugin: building flex project without >> > mavenizing Flex binaries >> > >> > Le 29/04/2014 09:59, Christofer Dutz a écrit : >> > > - Publish a release of Apache Flex to Apaches Maven Repo >> > > >> > > And then you'd be able to build Apache Flex projects without having >> > > to >> > mavenize anything yourself. >> > Including airglobal, playerglobal and the like ... ? >> > There would be provided on an adobe repository or the would allow us >> > to host those binary blobs ? >> > >> >> >> >> -- >> WBR >> Maxim aka solomax >> > > > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax
