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 3DD02DBF8 for ; Tue, 25 Sep 2012 06:04:41 +0000 (UTC) Received: (qmail 43078 invoked by uid 500); 25 Sep 2012 06:04:40 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 42936 invoked by uid 500); 25 Sep 2012 06:04:39 -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 42903 invoked by uid 99); 25 Sep 2012 06:04:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2012 06:04:38 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FRT_ADOBE2,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [80.67.31.94] (HELO smtprelay05.ispgateway.de) (80.67.31.94) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2012 06:04:32 +0000 Received: from [10.128.0.22] (helo=exchange.df.eu) by smtprelay05.ispgateway.de with esmtps (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1TGOFf-0006Dy-Sd for flex-dev@incubator.apache.org; Tue, 25 Sep 2012 08:04:11 +0200 Received: from ECCR06PUBLIC.exchange.local ([10.128.2.55]) by efe07.exchange.local ([10.128.0.22]) with mapi; Tue, 25 Sep 2012 07:59:09 +0200 From: "christofer.dutz@c-ware.de" To: "flex-dev@incubator.apache.org" Date: Tue, 25 Sep 2012 07:59:07 +0200 Subject: AW: AW: Flex Maven FDK Generator RC1 Thread-Topic: AW: Flex Maven FDK Generator RC1 Thread-Index: Ac2alXdHsUe93VxTTi2MHXoKSleQqAATQ4rA Message-ID: <66E38C42347D6446BF7FCB22C3D3878072DDC95B95@ECCR06PUBLIC.exchange.local> References: <66E38C42347D6446BF7FCB22C3D3878072DDC95A9A@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, Actually I get a lot of requests for the older FDKs as only one of the patc= hed versions is available and most people don't want to use the un-patched = ones. But I agree ... the problem should not apply to Apache FDKs. Unfortunately = they do have dependencies to the playerglobal and airglobal and these are c= urrently deployed in a rather undesirable way :-( Chris -----Urspr=FCngliche Nachricht----- Von: carlos.rovira@gmail.com [mailto:carlos.rovira@gmail.com] Im Auftrag vo= n Carlos Rovira Gesendet: Montag, 24. September 2012 22:45 An: flex-dev@incubator.apache.org Betreff: Re: AW: Flex Maven FDK Generator RC1 Hi, the problem is with adobe sdks only, but apache flex sdks would not have th= is problem isn't it? for older sdks up to 4.5.1 the artifacts are available from maven official = repo, but 4.6 is the only one not deployed. The next is already apache flex= 4.8, that should not have any legal problems... I'm missing something? 2012/9/24 Alex Harui : > Chris, > > IMO, even a download link to the actual Adobe binaries stored on a=20 > non-Adobe site is not legal. I believe that any final structure will=20 > require downloading Adobe binaries from Adobe or some third party that=20 > has a license to do so. Imagine this was an MP3 file: you are=20 > restricted from sharing music without permission of the artist. > > What would be the minimum change Adobe would need to allow you to get=20 > the Adobe stuff from Adobe? Would I just need to place pom.xml files=20 > next to the zips for AIR SDK and Player? If so, I will look into=20 > getting that to happen. What would go in the pom.xml files? > > > On 9/24/12 4:50 AM, "christofer.dutz@c-ware.de"=20 > > wrote: > >> Hi Carlos, >> >> I could whip up a "dummy" version of my FDKs replacing the binary=20 >> artifacts with empty placeholders of the same name. This way there=20 >> shouldn't be any legal issues with me publically making Adobe stuff down= loadable. >> The other alternative would be that everyone interested in the=20 >> Structure to contact me and I'll give them the download link (I just=20 >> don't want to get into Trouble with Adobe). >> >> 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 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=20 >> discuss project structure to get parent/child, and so on... >> >> I think a new [Discuss] thread should be open ASAP to see everyone=20 >> 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=20 >>> Mavenized form. With the Tool it should be almost no work at all.=20 >>> Frederic added a tool to deploy the generated artifacts to Nexus, I=20 >>> am planning on creating something similar to deploy to Artifactory=20 >>> (I haven't checked, if I even need to implement a separate tool).=20 >>> Using these it should be easy to integrate them into the release=20 >>> build. If any maven/ant plugin adapters are needed I would be glad to p= rovide them. >>> >>> The first step to mavenizing Flex is do decide on the structure of=20 >>> the project. I think my Generator is a first step in this direction=20 >>> and that's one of the reasons why I would like to open the discussion o= n the structure. >>> My FDKs are my opinion on an ideal structure but I would be glad to=20 >>> adjust if someone has any objections. >>> >>> The poms are very simple. They don't contain the maven config needed=20 >>> to build. 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=20 >>> necessary to add the parent/child module config stuff, the plugin=20 >>> configuration stuff, the dependencies and so on. >>> But even if it would not be a simple "drop in the poms" process, I=20 >>> 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=20 >>> 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=20 >>> mavenized flex artifacts...could this be integrated in the build=20 >>> process to apache flex to have official apache flex maven artifacts? >>> >>> Going one step further... would be possible to create pom.xml for=20 >>> each apache flex project to create flex maven artificats from now=20 >>> on? This could generate maven flex artifacts from source code with=20 >>> jenkins as part of the normal apache flex sdk generation process and=20 >>> could be deployed to apache maven 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 >>>> 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 >>>> tp://repository.sonatype.org/content/sites/maven-sites/flexmojos/4. >>>> 0-RC2/com=20 >>>> pile-swc-mojo.html#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFlex >>>> mojosForS >>>> 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#iKnowWhatImDoingPleaseBreakMyBuildIwontBlameFl >>>> exmojosFo >>>> rStopWorking). >>>> 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=20 >>>> it 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=20 >>>> 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=20 >>>> explicit versions of each library of the FDK and can be used by=20 >>>> importing this artifact into your projects dependency=20 >>>> management.**** >>>> >>>> **5. **There is no longer a "framwework-config-zip", instead the= re >>>> 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=20 >>>> theme)**** >>>> >>>> **6. **If a library in the framework has a matching "rsl" or "sw= z" >>>> 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 vers= ion. >>>> Deploying them with the version of the FDK breaks the ability to=20 >>>> 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=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=20 >>>> 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=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=20 >>> Per=F3n, >>> 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 > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > -- 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