Hi Aley, Well I think the only references to Adobe stuff in the Apache Flex FDKs are the references to Playerglobal, Airglobal, Osmf and Textlayout (Am I missing any). Fortunately most of them are already out there and we could simply reference them. But you are right, that if we are not allowed to publish these anywhere public, that Adobe would have to do so.
My intention on creating the Generator was more of a "Download the official FDK, run the Generator, use the mavenized FDKs it outputs" approach. I don't think there should be any legal issues with that, should there? After all, it's just copying the files of your FDK around on your own computer and generating some xml files and isn't downloading anything from elsewhere. Chris -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Dienstag, 25. September 2012 18:00 An: flex-dev@incubator.apache.org Betreff: Re: Flex Maven FDK Generator RC1 Not too far in the future, the Falcon compiler will (can be) a separate independent build script. The rest of the framework will not have any Java code anymore. That might make it easier, so don't spend too much time on this unless you really need to retrofit old SDKs. I'm a bit confused by the "generator" and what is quoted below. If we wanted to create maven artifacts for the official maven repo, we certainly can't bundle in Adobe stuff, so wouldn't that require that Adobe either publishes to the official maven repo or at minimum puts up its own pom.xmls on its site so maven can pull the Adobe stuff from there? On 9/24/12 11:45 PM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote: > "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<h >> t >> > tp://repository.sonatype.org/content/sites/maven-sites/flexmojos/4.0-R > C2/com > pile-swc-mojo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmoj > osForS > topWorking>configuration option do disable this check ( > http://repository.sonatype.org/content/sites/maven-sites/flexmojos/4.0 > -RC2/c > ompile-swc-mojo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexm > ojosFo > rStopWorking). >> Even if you don¹t 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 didn¹t 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 >> I¹ll send you the link to the download (Don¹t want to publish that >> here). I will continue to make Flexmojos work with my new FDKs as >> soon as that¹s 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 > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
