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 B523CCB34 for ; Tue, 22 May 2012 21:50:25 +0000 (UTC) Received: (qmail 18125 invoked by uid 500); 22 May 2012 21:50:25 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 18090 invoked by uid 500); 22 May 2012 21:50:25 -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 18079 invoked by uid 99); 22 May 2012 21:50:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 21:50:24 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates 64.18.1.191 as permitted sender) Received: from [64.18.1.191] (HELO exprod6og106.obsmtp.com) (64.18.1.191) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 21:50:17 +0000 Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob106.postini.com ([64.18.5.12]) with SMTP ID DSNKT7wKBNt75W7ghqTUOIMK4rB6ducxXnT4@postini.com; Tue, 22 May 2012 14:49:57 PDT Received: from inner-relay-4.eur.adobe.com (inner-relay-4.adobe.com [193.104.215.14]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q4MLlgJ0027781 for ; Tue, 22 May 2012 14:47:42 -0700 (PDT) Received: from nahub01.corp.adobe.com (nahub01.corp.adobe.com [10.8.189.97]) by inner-relay-4.eur.adobe.com (8.12.10/8.12.9) with ESMTP id q4MLnVYx009088 for ; Tue, 22 May 2012 14:49:54 -0700 (PDT) Received: from NAMBX02.corp.adobe.com ([10.8.127.96]) by nahub01.corp.adobe.com ([10.8.189.97]) with mapi; Tue, 22 May 2012 14:49:39 -0700 From: Alex Harui To: "flex-dev@incubator.apache.org" Date: Tue, 22 May 2012 14:49:38 -0700 Subject: Re: AW: AW: AW: Library Versions used in Flex SDK Thread-Topic: AW: AW: AW: Library Versions used in Flex SDK Thread-Index: Ac00+SOpIuLkE5WnRsmregOJEexCBgAAMbdQAAV2oMcALKsswAAHEUcBABs0siAAhk/LqQ== Message-ID: In-Reply-To: <66E38C42347D6446BF7FCB22C3D3878072C670A974@ECCR06PUBLIC.exchange.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-Entourage/13.11.0.110726 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org On 5/22/12 5:41 AM, "christofer.dutz@c-ware.de" wrote: > I allready feared that there could be problems with legal issues in > distributing the runtimes. I guess the only solution would be do publish = the > tool to enable people to generate their own SDK versions (including the f= lash > players and playerglobals). I'm open to trying to see if Adobe can create artifacts for the Flash and AIR SDKs. I have no idea of what it would take. >=20 > Flexmojos is not only a link between Flex and Maven, but integrates sever= al > other tools, that make it extremely valuable: > - Apparat Integration to optimize the SWFs and SWCs > - GraniteDS to automatically generate the ActionScript model classes from > their Java counterparts. > So simply integrating the basic compiler feature would strip a lot of it'= s > functionality.=20 What percentage of users are using this functionality? Might be best to hi= t the sweet spot and have everything else be optional? > It would be great however if the compiler would could be called > directly instead of having to go the way of simulating the commandline ca= ll. What would that look like? >=20 > I know that Flexmojos still has quite some issues, but most of the Issues= I > had to resolve were mainly related to problems in the Flex compiler code = (Just > to mention one: Try using ASDoc with code comments containing the "@" > character ;-) ). I toally agree that the general perspective should be to > integrate the functionality of flexmojos into Flex, or at least have them > maintained by the same group, but I think the current SDK has far too man= y > issues that should be adressed first. The Adobe SDKs are important to folks and you are welcome to do what you ca= n with them. This thread is about the Apache Flex SDKs and we have more flexibility. > Trying to create a new Maven integration > layer would just add more to the todo list. So for now I think it would b= e > great to work together. I would be glad to contribute to make Flex work > better.=20 Make sure you get the IP issues resolved and we'll be glad to have your contributions. > As soon as the main issues are resolved I would also be glad to help > you create something similar or to integrate flexmojos to flex. >=20 > I'm also not requesting to change flex in any way to make mavenizing the = sdk > easier.=20 Earlier you said the current SDK has far too many issues. What are these issues and how do we address them without changing Flex? > Currently I was only suggesting to clean up the structure of the SDK > to more reflect the parts natures and to generate some helpfull other stu= ff > that makes life of people using it a lot easier: > - Generate a special pom containing only dependencyManagement section. Th= is > can be imported into other maven projects to automatically set the versio= ns of > the sdk artifacts. No idea what that means, but by all means, show us what needs to be done. > - Generate a special jar containing metadata that can be used by flexmojo= s to > perform validation (minimum SFW-version, minimum playerglobal version, et= c.). > Just to name a few. If this would be useful if we Apache had its own mapping to Maven, then fee= l free to show us what needs to be done here as well. --=20 Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui