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 49192DEF3 for ; Wed, 26 Sep 2012 07:26:56 +0000 (UTC) Received: (qmail 47245 invoked by uid 500); 26 Sep 2012 07:26:55 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 47044 invoked by uid 500); 26 Sep 2012 07:26:54 -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 47024 invoked by uid 99); 26 Sep 2012 07:26:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 07:26:53 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=FRT_ADOBE2,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of webdoublefx@hotmail.com designates 65.55.111.111 as permitted sender) Received: from [65.55.111.111] (HELO blu0-omc2-s36.blu0.hotmail.com) (65.55.111.111) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 07:26:45 +0000 Received: from BLU162-W19 ([65.55.111.71]) by blu0-omc2-s36.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 26 Sep 2012 00:26:24 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_3c53455d-de4e-4686-9cf8-ba5486f08d52_" X-Originating-IP: [82.247.153.175] From: =?iso-8859-15?B?RnLpZOlyaWMgVEhPTUFT?= To: "flex-dev@incubator.apache.org" Subject: RE: AW: Flex Maven FDK Generator RC1 Date: Wed, 26 Sep 2012 09:26:24 +0200 Importance: Normal In-Reply-To: <66E38C42347D6446BF7FCB22C3D3878072DE7C727C@ECCR06PUBLIC.exchange.local> References: ,,<66E38C42347D6446BF7FCB22C3D3878072DE7C727C@ECCR06PUBLIC.exchange.local> MIME-Version: 1.0 X-OriginalArrivalTime: 26 Sep 2012 07:26:24.0629 (UTC) FILETIME=[3BFC4A50:01CD9BB8] --_3c53455d-de4e-4686-9cf8-ba5486f08d52_ Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Hi Chris=2C We were writting in the same time :) I think you greatly answered the 2nd p= oint. Fr=E9d=E9ric THOMAS > From: christofer.dutz@c-ware.de > To: flex-dev@incubator.apache.org > Date: Wed=2C 26 Sep 2012 08:59:16 +0200 > Subject: AW: Flex Maven FDK Generator RC1 >=20 > Hi Aley=2C >=20 > Well I think the only references to Adobe stuff in the Apache Flex FDKs a= re the references to Playerglobal=2C Airglobal=2C 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=2C that if we are not allowed to publish these anywhere= public=2C that Adobe would have to do so.=20 >=20 > My intention on creating the Generator was more of a "Download the offici= al FDK=2C run the Generator=2C use the mavenized FDKs it outputs" approach.= I don't think there should be any legal issues with that=2C should there? = After all=2C it's just copying the files of your FDK around on your own com= puter and generating some xml files and isn't downloading anything from els= ewhere. >=20 > Chris >=20 >=20 >=20 > -----Urspr=FCngliche Nachricht----- > Von: Alex Harui [mailto:aharui@adobe.com]=20 > Gesendet: Dienstag=2C 25. September 2012 18:00 > An: flex-dev@incubator.apache.org > Betreff: Re: Flex Maven FDK Generator RC1 >=20 > Not too far in the future=2C the Falcon compiler will (can be) a separate= independent build script. The rest of the framework will not have any Jav= a code anymore. That might make it easier=2C so don't spend too much time = on this unless you really need to retrofit old SDKs. >=20 > I'm a bit confused by the "generator" and what is quoted below. If we wa= nted to create maven artifacts for the official maven repo=2C we certainly = can't bundle in Adobe stuff=2C so wouldn't that require that Adobe either p= ublishes 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? >=20 >=20 >=20 >=20 > On 9/24/12 11:45 PM=2C "Fr=E9d=E9ric THOMAS" wr= ote: >=20 > > "Going one step further... would be possible to create pom.xml for=20 > > each apache flex project to create flex maven artificats from now on?=20 > > This could generate maven flex artifacts from source code with jenkins= =20 > > as part of the normal apache flex sdk generation process and could be=20 > > deployed to apache maven official repo." > >=20 > > Hi=2C > >=20 > > Actually=2C the framework doesn't seems so hard to mavenized=2C what is= =20 > > more difficult to me would be the compiler part which has to be done=20 > > before the framework as among other things FM uses the same compiler=20 > > version the framework has=2C in more it seems logical to keep everythin= g=20 > > as a bundle=2C I'm then looking at a way to mavenized the compiler part= =20 > > using ant maven plugging but doesn't look so easy either=2C may be a=20 > > little bit more=2C I'll keep in touch. > >=20 > > Fr=E9d=E9ric THOMAS. > >=20 > > -----Original Message----- > > From: carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] On=20 > > Behalf Of Carlos Rovira > > Sent: Monday=2C September 24=2C 2012 12:24 PM > > To: flex-dev@incubator.apache.org > > Subject: Re: Flex Maven FDK Generator RC1 > >=20 > > Hi Chris=2C > >=20 > > this sounds very good. The point 5 should be the solution to the=20 > > problem we had with themes. I would like to have access to the link in= =20 > > order to test it. > >=20 > > btw=2C if this works and we finaly have a working process to have=20 > > mavenized flex artifacts...could this be integrated in the build=20 > > process to apache flex to have official apache flex maven artifacts? > >=20 > > Going one step further... would be possible to create pom.xml for each= =20 > > apache flex project to create flex maven artificats from now on? This=20 > > could generate maven flex artifacts from source code with jenkins as=20 > > part of the normal apache flex sdk generation process and could be=20 > > deployed to apache maven official repo. > >=20 > > Great work! :) > >=20 > >=20 > >=20 > >=20 > > 2012/9/24 christofer.dutz@c-ware.de > >=20 > >> Hi=2C**** > >>=20 > >> ** ** > >>=20 > >> I just wanted to inform you=2C 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.**** > >>=20 > >> ** ** > >>=20 > >> 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).**** > >>=20 > >> You should be able to compile using Velos famous=20 > >> iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexmojosForStopWorking >> t > >>=20 > > tp://repository.sonatype.org/content/sites/maven-sites/flexmojos/4.0-R > > C2/com=20 > > 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=20 > > ompile-swc-mojo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlexm > > ojosFo > > rStopWorking). > >> Even if you don=B9t 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 =A6 as soon as Deployments are=20 > >> available=2C this would be hard to fix.**** > >>=20 > >> ** ** > >>=20 > >> Things that are different from Velos Deployments:**** > >>=20 > >> ** ** > >>=20 > >> **1. **Flash player stuff is now in =B3com.adobe.flash.framework= =B2 > >> (The playerglobals are here) and =B3com.adobe.flash.runtime=B2 (The=20 > >> Flashplayer executable binaries are here) (There is no longer any=20 > >> =B3playerglobal-{fdk-version}-{player-version}.swc=B2 artifacts)**** > >>=20 > >> **2. **Air stuff is now in =B3com.adobe.air.framework=B2 (The > >> airglobals are here) (I didn=B9t make it deploy the air runtime as thi= s=20 > >> would have been really tricky)**** > >>=20 > >> **3. **Adobe FDKs are under =B3com.adobe.flex=B2 and Apache FDKs= are > >> under =B3org.apache.flex=B2**** > >>=20 > >> **4. **There are new Artifacts > >> =B3com.adobe.flex:framework:{fdk-version}:pom=B2 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.**** > >>=20 > >> **5. **There is no longer a =B3framwework-config-zip=B2=2C inste= ad there > >> is a swc-Theme for every theme of a FDK under=20 > >> =B3com.adobe.flex.framework.themes=B2 (During deployment I use compc t= o=20 > >> compile a SWC from every theme that is not already an SWC theme)**** > >>=20 > >> **6. **If a library in the framework has a matching =B3rsl=B2 or= =B3swz=B2 > >> the versions of these are used to deploy the artifact (generally=20 > >> affects =B3osmf=B2 and =B3textlayout=B2 but in the A and B versions of= =20 > >> patched FDKs the versions of =B3framework=B2 etc. differ from the FDK = version. > >> Deploying them with the version of the FDK breaks the ability to load= =20 > >> the SWZ files from an Adobe server)**** > >>=20 > >> ** ** > >>=20 > >> I think that was the major stuff =3B-)**** > >>=20 > >> ** ** > >>=20 > >> If someone wants to have a look at the FDKs=2C please contact me and=20 > >> I=B9ll send you the link to the download (Don=B9t want to publish that= =20 > >> here). I will continue to make Flexmojos work with my new FDKs as=20 > >> soon as that=B9s finished and seems to be working I would like to make= =20 > >> the Generator publically > >> available.**** > >>=20 > >> ** ** > >>=20 > >> Chris**** > >>=20 > >> ** ** > >>=20 > >> ** ** > >>=20 > >> [ C h r i s t o f e r D u t z ]**** > >>=20 > >> ** ** > >>=20 > >> C-Ware IT-Service**** > >>=20 > >> Inhaber**** > >>=20 > >> Dipl. Inf. Christofer Dutz**** > >>=20 > >> Karlstra=DFe. 104=2C 64285 Darmstadt**** > >>=20 > >> ** ** > >>=20 > >> [image: Beschreibung: > >> 788335] > >> **** > >>=20 > >> IT- und > >> Systemh=E4user > >> **** > >>=20 > >> ** ** > >>=20 > >> fon: 0 61 51 / 27315 - 61**** > >>=20 > >> fax: 0 61 51 / 27315 - 64**** > >>=20 > >> mobil: 0171 / 7 444 2 33**** > >>=20 > >> email: christofer.dutz@c-ware.de**** > >>=20 > >> http://www.c-ware.de**** > >>=20 > >> ** ** > >>=20 > >> UStId-Nr. DE195700962**** > >>=20 > >> ** ** > >>=20 > >> ** ** > >>=20 > >=20 > >=20 > >=20 > > -- > > 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= =2C=20 > > 32 Planta 10=2C Puertas P-Q > > 28020 Madrid > >=20 >=20 > -- > Alex Harui > Flex SDK Team > Adobe Systems=2C Inc. > http://blogs.adobe.com/aharui >=20 = --_3c53455d-de4e-4686-9cf8-ba5486f08d52_--