"Going one step further... would be possible to create pom.xml for each apache flex project to create flex maven artificats from now on? This could generate maven flex artifacts from source code with jenkins as part of the normal apache flex sdk generation process and could be deployed to apache maven official repo."
Hi, Actually, the framework doesn't seems so hard to mavenized, what is more difficult to me would be the compiler part which has to be done before the framework as among other things FM uses the same compiler version the framework has, in more it seems logical to keep everything as a bundle, I'm then looking at a way to mavenized the compiler part using ant maven plugging but doesn't look so easy either, may be a little bit more, I'll keep in touch. Frédéric THOMAS. -----Original Message----- From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of Carlos Rovira Sent: Monday, September 24, 2012 12:24 PM To: flex-dev@incubator.apache.org Subject: Re: Flex Maven FDK Generator RC1 Hi Chris, this sounds very good. The point 5 should be the solution to the problem we had with themes. I would like to have access to the link in order to test it. btw, if this works and we finaly have a working process to have mavenized flex artifacts...could this be integrated in the build process to apache flex to have official apache flex maven artifacts? Going one step further... would be possible to create pom.xml for each apache flex project to create flex maven artificats from now on? This could generate maven flex artifacts from source code with jenkins as part of the normal apache flex sdk generation process and could be deployed to apache maven official repo. Great work! :) 2012/9/24 christofer.d...@c-ware.de <christofer.d...@c-ware.de> > Hi,**** > > ** ** > > I just wanted to inform you, that I have somewhat finished my Flex FDK > Generator. With this tool you should be able to generate Mavenized > FDKs from any existing Flex FDK (Apache or Adobe) and Air SDK.**** > > ** ** > > In order to use the new FDKs with Flexmojos 6.x I still have to change > some stuff in Flexmojos 6.x (The framework.swc now has the version of > the swz and this sometimes differs from the FDK version and hereby > from the compiler.jar version).**** > > You should be able to compile using Velos famous > iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmojosForStopWorking<ht > tp://repository.sonatype.org/content/sites/maven-sites/flexmojos/4.0-RC2/com pile-swc-mojo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmojosForS topWorking>configuration option do disable this check ( http://repository.sonatype.org/content/sites/maven-sites/flexmojos/4.0-RC2/c ompile-swc-mojo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmojosFo rStopWorking). > Even if you dont want to actually use Flexmojos 6.x it would be great > to get some feedback on the deployment structure. Currently it would > be easy to change things as soon as Deployments are available, this > would be hard to fix.**** > > ** ** > > Things that are different from Velos Deployments:**** > > ** ** > > **1. **Flash player stuff is now in com.adobe.flash.framework > (The playerglobals are here) and com.adobe.flash.runtime (The > Flashplayer executable binaries are here) (There is no longer any > playerglobal-{fdk-version}-{player-version}.swc artifacts)**** > > **2. **Air stuff is now in com.adobe.air.framework (The > airglobals are here) (I didnt make it deploy the air runtime as this > would have been really tricky)**** > > **3. **Adobe FDKs are under com.adobe.flex and Apache FDKs are > under org.apache.flex**** > > **4. **There are new Artifacts > com.adobe.flex:framework:{fdk-version}:pom which define the explicit > versions of each library of the FDK and can be used by importing this > artifact into your projects dependency management.**** > > **5. **There is no longer a framwework-config-zip, instead there > is a swc-Theme for every theme of a FDK under > com.adobe.flex.framework.themes (During deployment I use compc to > compile a SWC from every theme that is not already an SWC theme)**** > > **6. **If a library in the framework has a matching rsl or swz > the versions of these are used to deploy the artifact (generally > affects osmf and textlayout but in the A and B versions of patched > FDKs the versions of framework etc. differ from the FDK version. > Deploying them with the version of the FDK breaks the ability to load > the SWZ files from an Adobe server)**** > > ** ** > > I think that was the major stuff ;-)**** > > ** ** > > If someone wants to have a look at the FDKs, please contact me and > Ill send you the link to the download (Dont want to publish that > here). I will continue to make Flexmojos work with my new FDKs as soon > as thats finished and seems to be working I would like to make the > Generator publically > available.**** > > ** ** > > Chris**** > > ** ** > > ** ** > > [ C h r i s t o f e r D u t z ]**** > > ** ** > > C-Ware IT-Service**** > > Inhaber**** > > Dipl. Inf. Christofer Dutz**** > > Karlstraße. 104, 64285 Darmstadt**** > > ** ** > > [image: Beschreibung: > 788335]<http://www.benchpark.com/788335/kundenzufriedenheit.htm> > **** > > IT- und > Systemhäuser<http://www.benchpark.com/it_und_systemhaeuser.htm> > **** > > ** ** > > fon: 0 61 51 / 27315 - 61**** > > fax: 0 61 51 / 27315 - 64**** > > mobil: 0171 / 7 444 2 33**** > > email: christofer.d...@c-ware.de**** > > http://www.c-ware.de**** > > ** ** > > UStId-Nr. DE195700962**** > > ** ** > > ** ** > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 35 57 77 <http://www.codeoscopic.com> CODEOSCOPIC S.A. <http://www.codeoscopic.com> Avd. del General Perón, 32 Planta 10, Puertas P-Q 28020 Madrid
