Return-Path: X-Original-To: apmail-flex-users-archive@www.apache.org Delivered-To: apmail-flex-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8DD1E11084 for ; Tue, 24 Jun 2014 11:47:19 +0000 (UTC) Received: (qmail 37221 invoked by uid 500); 24 Jun 2014 11:47:19 -0000 Delivered-To: apmail-flex-users-archive@flex.apache.org Received: (qmail 37181 invoked by uid 500); 24 Jun 2014 11:47:19 -0000 Mailing-List: contact users-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@flex.apache.org Delivered-To: mailing list users@flex.apache.org Received: (qmail 37169 invoked by uid 99); 24 Jun 2014 11:47:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jun 2014 11:47:18 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of solomax666@gmail.com designates 209.85.214.170 as permitted sender) Received: from [209.85.214.170] (HELO mail-ob0-f170.google.com) (209.85.214.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jun 2014 11:47:14 +0000 Received: by mail-ob0-f170.google.com with SMTP id uz6so165205obc.15 for ; Tue, 24 Jun 2014 04:46:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ixj0nXO0ue8sjNx2KS0R+QKc8tDx6M33drL/eViLzl4=; b=NYlUC6S+FNXQtNES76UlyJdkXngDxLu+aTt5Zqih+JQQ3S3YfT8qKzeaDGM1UvHpph S41+/x+jb3/2o6y9ahqM0gvwhd8Argdduv9muxGwbP903eStbiOp1BKp5T6DkPv8KMBO QyQl75qDOjwzWjKbMWG4joMU5FbCHggnGD4u6atrT00r+RMsoBzRMOFCs0HSjGUEa3hv v5HKaEhNsCPPX1bnYYJroHDO2YBQZp6VJNDNoczftyewG3pl7q37+FsQaVgz6vQsJZxg gxmrlI4oBT9/DgWiagmvaciVz/efFiCmCOFhmAlUyM0RBL4xCTCx0KfsXn44kpd9EOgR AoNA== MIME-Version: 1.0 X-Received: by 10.182.143.37 with SMTP id sb5mr436953obb.76.1403610413871; Tue, 24 Jun 2014 04:46:53 -0700 (PDT) Received: by 10.182.71.66 with HTTP; Tue, 24 Jun 2014 04:46:53 -0700 (PDT) In-Reply-To: <1403609539146.94103@c-ware.de> References: <1398758353418.2034@c-ware.de> <53600196.5020201@zone84.net> <1398843038121.15970@c-ware.de> <4195e81b6c8a499aa373ea7ba7e9fd77@AMSPR05MB226.eurprd05.prod.outlook.com> <34f0d97b233949b4a8ad8aa0c4845401@DBXPR05MB237.eurprd05.prod.outlook.com> <1403609539146.94103@c-ware.de> Date: Tue, 24 Jun 2014 18:46:53 +0700 Message-ID: Subject: Re: AW: flexmojos-maven-plugin: building flex project without mavenizing Flex binaries From: Maxim Solodovnik To: users@flex.apache.org Content-Type: multipart/alternative; boundary=e89a8ff1c9fe1f388b04fc938441 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff1c9fe1f388b04fc938441 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Great ! Thanks :) Will wait this huge release :) On 24 June 2014 18:32, Christofer Dutz wrote: > Yes actually there are updates: > - Flexmojos now works with the new mavenized fdks > - I removed a lot of legacy stuff, that made flexmojos depend on flex 2 > and flex 3 from Adobe > - The testsuite is now 100% green and I wanted to commit those changes as > soon as I had the time to review the changes again (will probably be a ve= ry > large commit) > - As soon as that's out, I would need to somehow release the mavenizer so > I can deploy the libs to Apaches Central Maven Repo (I still want to do o= ne > change before triggering this release) > - As soon as the mavenizer is released, we could discuss releasing an > Apache Flex SDK as Maven artifacts, by running the Mavanizer against the > rellease version and using the Mavenizers deployer to upload everything. > - After that's done I can use those libs from Flexmojos and implement the > last step needed to auto-download and mavenize Flex and Air artifacts. > > So I would state that the technical difficulties have been solved, all I > need to do is implement one further module for Flexmojos that simply > integrates a call to the mavenizer from a maven build. The rest is just > paperwork ;-) > > Chris > > > ________________________________________ > Von: Maxim Solodovnik > Gesendet: Dienstag, 24. Juni 2014 13:14 > An: users@flex.apache.org > Betreff: Re: AW: flexmojos-maven-plugin: building flex project without > mavenizing Flex binaries > > Hello Chris, > Any updates on this issue? > > > On 30 May 2014 22:54, Maxim Solodovnik wrote: > > > Thanks for the update :) > > Also will have a vacation (hopefully) > > Please let me know if you need any help with testing :) > > > > > > On Fri, May 30, 2014 at 10:50 PM, Christofer Dutz < > > christofer.dutz@c-ware.de> wrote: > > > >> Well currently I'm a little consumed with other tasks. I did do a litt= le > >> testing in building Flexmojos with the new FDKs and it seems I will > have to > >> do a little more tweaking of the generated poms (It seems I will have = to > >> generate the dependency management stuff into a new pom similar to the > way > >> I initially did it). > >> But I doubt I'll be able to finish this this week and then I'm going t= o > >> be on vacation ... so stay tuned, but don't expect something useable i= n > the > >> next 2-3 Weeks. > >> > >> Chris > >> > >> > >> -----Urspr=C3=BCngliche Nachricht----- > >> Von: Maxim Solodovnik [mailto:solomax666@gmail.com] > >> Gesendet: Freitag, 30. Mai 2014 16:55 > >> An: users@flex.apache.org > >> Betreff: Re: AW: flexmojos-maven-plugin: building flex project without > >> mavenizing Flex binaries > >> > >> 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 < > solomax666@gmail.com> > >> wrote: > >> > >> > Thanks for the update Chris :) > >> > Looking forward to test it :) > >> > > >> > > >> > On Fri, May 16, 2014 at 3:54 AM, Christofer Dutz < > >> > christofer.dutz@c-ware.de> 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 a= n > >> >> 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=C3=BCngliche Nachricht----- > >> >> Von: Maxim Solodovnik [mailto:solomax666@gmail.com] > >> >> Gesendet: Donnerstag, 8. Mai 2014 16:26 > >> >> An: users@flex.apache.org > >> >> 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 > >> >> wrote: > >> >> > >> >> > Well actually Alex and I have discussed that I will be implementi= ng > >> >> > 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 versio= n. > >> >> > 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 companie= s > >> 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 Plugi= n > >> >> > I started working on a while ago. > >> >> > > >> >> > So far what we have planned. > >> >> > > >> >> > Chris > >> >> > > >> >> > > >> >> > ________________________________________ > >> >> > Von: Simon Morvan > >> >> > Gesendet: Dienstag, 29. April 2014 21:46 > >> >> > An: users@flex.apache.org > >> >> > Betreff: Re: AW: flexmojos-maven-plugin: building flex project > >> >> > without mavenizing Flex binaries > >> >> > > >> >> > Le 29/04/2014 09:59, Christofer Dutz a =C3=A9crit : > >> >> > > - 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 > >> > > > > > > > > -- > > WBR > > Maxim aka solomax > > > > > > -- > WBR > Maxim aka solomax > --=20 WBR Maxim aka solomax --e89a8ff1c9fe1f388b04fc938441--