Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A48B6D96D for ; Mon, 24 Sep 2012 11:51:07 +0000 (UTC) Received: (qmail 59167 invoked by uid 500); 24 Sep 2012 11:51:06 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 59083 invoked by uid 500); 24 Sep 2012 11:51:06 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 59057 invoked by uid 99); 24 Sep 2012 11:51:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2012 11:51:05 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [80.67.18.13] (HELO smtprelay01.ispgateway.de) (80.67.18.13) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2012 11:50:59 +0000 Received: from [10.128.0.1] (helo=exchange.df.eu) by smtprelay01.ispgateway.de with esmtps (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1TG7BP-0001Y5-9q for flex-dev@incubator.apache.org; Mon, 24 Sep 2012 13:50:39 +0200 Received: from ECCR06PUBLIC.exchange.local ([10.128.2.55]) by efe01.exchange.local ([10.128.0.1]) with mapi; Mon, 24 Sep 2012 13:50:35 +0200 From: "christofer.dutz@c-ware.de" To: "flex-dev@incubator.apache.org" Date: Mon, 24 Sep 2012 13:50:34 +0200 Subject: AW: Flex Maven FDK Generator RC1 Thread-Topic: Flex Maven FDK Generator RC1 Thread-Index: Ac2aSSCu3H8GO4I5SZKhyCMYkPDhagAAUh3A Message-ID: <66E38C42347D6446BF7FCB22C3D3878072DDC95A9A@ECCR06PUBLIC.exchange.local> References: <66E38C42347D6446BF7FCB22C3D3878072DDC95A61@ECCR06PUBLIC.exchange.local> <66E38C42347D6446BF7FCB22C3D3878072DDC95A81@ECCR06PUBLIC.exchange.local> In-Reply-To: Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi Carlos, I could whip up a "dummy" version of my FDKs replacing the binary artifacts= with empty placeholders of the same name. This way there shouldn't be any = legal issues with me publically making Adobe stuff downloadable.=20 The other alternative would be that everyone interested in the Structure to= contact me and I'll give them the download link (I just don't want to get = into Trouble with Adobe). Chris=20 -----Urspr=FCngliche Nachricht----- Von: carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] Im Auftrag vo= n Carlos Rovira Gesendet: Montag, 24. September 2012 13:32 An: flex-dev@incubator.apache.org Betreff: Re: Flex Maven FDK Generator RC1 Hi Chris, you're completly right. In order to get this milestone we need to discuss p= roject structure to get parent/child, and so on... I think a new [Discuss] thread should be open ASAP to see everyone opinion = about this. 2012/9/24 christofer.dutz@c-ware.de : > Hi Carlos, > > I was hoping that Apache would start publishing their FDKs in a Mavenized= form. With the Tool it should be almost no work at all. Frederic added a t= ool to deploy the generated artifacts to Nexus, I am planning on creating s= omething similar to deploy to Artifactory (I haven't checked, if I even nee= d to implement a separate tool). Using these it should be easy to integrate= them into the release build. If any maven/ant plugin adapters are needed I= would be glad to provide them. > > The first step to mavenizing Flex is do decide on the structure of the pr= oject. I think my Generator is a first step in this direction and that's on= e of the reasons why I would like to open the discussion on the structure. = My FDKs are my opinion on an ideal structure but I would be glad to adjust = if someone has any objections. > > The poms are very simple. They don't contain the maven config needed to b= uild. They even don't contain the dependency information needed to build. > In order to use the poms to build Flex in Maven it would make it necessar= y to add the parent/child module config stuff, the plugin configuration stu= ff, the dependencies and so on. > But even if it would not be a simple "drop in the poms" process, I think = it shouldn't be that hard. > > Chris > > > > -----Urspr=FCngliche Nachricht----- > Von: carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] Im=20 > Auftrag von Carlos Rovira > Gesendet: Montag, 24. September 2012 12:24 > An: flex-dev@incubator.apache.org > Betreff: 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 tes= t 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 f= lex to have official apache flex maven artifacts? > > Going one step further... would be possible to create pom.xml for each ap= ache flex project to create flex maven artificats from now on? This could g= enerate maven flex artifacts from source code with jenkins as part of the n= ormal apache flex sdk generation process and could be deployed to apache ma= ven official repo. > > Great work! :) > > > > > 2012/9/24 christofer.dutz@c-ware.de > >> Hi,**** >> >> ** ** >> >> I just wanted to inform you, that I have somewhat finished my Flex=20 >> FDK Generator. With this tool you should be able to generate=20 >> Mavenized FDKs from any existing Flex FDK (Apache or Adobe) and Air=20 >> SDK.**** >> >> ** ** >> >> In order to use the new FDKs with Flexmojos 6.x I still have to=20 >> change some stuff in Flexmojos 6.x (The framework.swc now has the=20 >> version of the swz and this sometimes differs from the FDK version=20 >> and hereby from the compiler.jar version).**** >> >> You should be able to compile using Velos famous=20 >> iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmojosForStopWorking> t=20 >> tp://repository.sonatype.org/content/sites/maven-sites/flexmojos/4.0-RC2= /compile-swc-mojo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmojo= sForStopWorking>configuration option do disable this check ( http://reposit= ory.sonatype.org/content/sites/maven-sites/flexmojos/4.0-RC2/compile-swc-mo= jo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmojosForStopWorking= ). >> Even if you don't want to actually use Flexmojos 6.x it would be=20 >> great to get some feedback on the deployment structure. Currently it=20 >> would be easy to change things . as soon as Deployments are=20 >> 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=20 >> Flashplayer executable binaries are here) (There is no longer any=20 >> "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=20 >> 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=20 >> explicit versions of each library of the FDK and can be used by=20 >> 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=20 >> "com.adobe.flex.framework.themes" (During deployment I use compc to=20 >> 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=20 >> affects "osmf" and "textlayout" but in the A and B versions of=20 >> patched FDKs the versions of "framework" etc. differ from the FDK versio= n. >> Deploying them with the version of the FDK breaks the ability to load=20 >> 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=20 >> I'll send you the link to the download (Don't want to publish that=20 >> here). I will continue to make Flexmojos work with my new FDKs as=20 >> soon as that's finished and seems to be working I would like to make=20 >> 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=DFe. 104, 64285 Darmstadt**** >> >> ** ** >> >> [image: Beschreibung: >> 788335] >> **** >> >> IT- und >> Systemh=E4user >> **** >> >> ** ** >> >> fon: 0 61 51 / 27315 - 61**** >> >> fax: 0 61 51 / 27315 - 64**** >> >> mobil: 0171 / 7 444 2 33**** >> >> email: christofer.dutz@c-ware.de**** >> >> http://www.c-ware.de**** >> >> ** ** >> >> UStId-Nr. DE195700962**** >> >> ** ** >> >> ** ** >> > > > > -- > Carlos Rovira > Director de Tecnolog=EDa > M: +34 607 22 60 05 > F: +34 912 35 57 77 > > CODEOSCOPIC S.A. Avd. del General Per=F3n,=20 > 32 Planta 10, Puertas P-Q > 28020 Madrid -- Carlos Rovira Director de Tecnolog=EDa M: +34 607 22 60 05 F: +34 912 35 57 77 CODEOSCOPIC S.A. Avd. del General Per=F3n, 32 Planta 10, Puertas P-Q 28020 Madrid