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 EC0D2DEF6 for ; Wed, 12 Sep 2012 20:20:14 +0000 (UTC) Received: (qmail 51982 invoked by uid 500); 12 Sep 2012 20:20:14 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 51954 invoked by uid 500); 12 Sep 2012 20:20:13 -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 51946 invoked by uid 99); 12 Sep 2012 20:20:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Sep 2012 20:20:13 +0000 X-ASF-Spam-Status: No, hits=-1.3 required=5.0 tests=FRT_ADOBE2,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gosmith@adobe.com designates 64.18.1.185 as permitted sender) Received: from [64.18.1.185] (HELO exprod6og103.obsmtp.com) (64.18.1.185) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Sep 2012 20:20:05 +0000 Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob103.postini.com ([64.18.5.12]) with SMTP ID DSNKUFDuX2csgXD939v9sKNxF6N70l0DqVKY@postini.com; Wed, 12 Sep 2012 13:19:45 PDT Received: from inner-relay-4.eur.adobe.com (inner-relay-4b [10.128.4.237]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q8CKJgL1002114; Wed, 12 Sep 2012 13:19:43 -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 q8CKJRSp016049; Wed, 12 Sep 2012 13:19:41 -0700 (PDT) Received: from nambx05.corp.adobe.com ([10.8.189.124]) by nahub01.corp.adobe.com ([10.8.189.97]) with mapi; Wed, 12 Sep 2012 13:19:37 -0700 From: Gordon Smith To: "flex-dev@incubator.apache.org" , Raju Bitter Date: Wed, 12 Sep 2012 13:19:36 -0700 Subject: RE: Is there anything the community can do to help you testing or documenting Falcon and the build process? Thread-Topic: Is there anything the community can do to help you testing or documenting Falcon and the build process? Thread-Index: Ac2Q7ERmbPNeV+ltT62j2p91tSgEdgAIfengAANdVrcAAe1coA== Message-ID: <149F8129B58B2D418508E63117D9C5419B3A89C33B@nambx05.corp.adobe.com> References: <149F8129B58B2D418508E63117D9C5419B3A89C28C@nambx05.corp.adobe.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: 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 > 0. Get the MXML handling working. Sorry, that isn't my 0th priority. If you can't even run mxmlc, it doesn't = matter whether mxmlc compiles MXML properly. And if people can't understand= how to build Falcon, then no one will be able to help me complete MXML. Fi= nally, the ActionScript side of the compiler is equally important given tha= t most people's MXML files have large amounts of ActionScript. - Gordon -----Original Message----- From: Alex Harui [mailto:aharui@adobe.com]=20 Sent: Wednesday, September 12, 2012 12:21 PM To: flex-dev@incubator.apache.org; Raju Bitter Subject: Re: Is there anything the community can do to help you testing or = documenting Falcon and the build process? On 9/12/12 10:52 AM, "Gordon Smith" wrote: > My top priorities currently are: 0. Get the MXML handling working. >=20 > 1. Get the top-level Ant targets working properly. For example, 'ant java= doc' > currently produces compilation errors, probably due to a classpath=20 > problem, and 'ant main' produces an mxmlc which doesn't work due to=20 > another classpath problem that you noticed. >=20 > 2. Document the build process, either on wiki pages or in the README=20 > file, so that people understand what environment variables need to be=20 > set and what Ant targets to use. >=20 > 3. Create JUnit tests in which Falcon builds each of the SDK SWCs. As=20 > part of this I want to change the SDK build scripts so that the=20 > tasks don't have a bunch of configuration but instead simply=20 > load a config file. Then the JUnit test can use the same config file=20 > to compile the SWC in a debuggable way by calling Falcon's COMPC.main() e= ntry point. >=20 > 4. Update the SDK code to suit Falcon, because it is stricter than the=20 > old compiler. >=20 > 5. Log bugs for any SDK code that Falcon barfs on (either throwing=20 > Java exceptions or reporting spurious errors or warnings). >=20 > 6. Fix those bugs. >=20 > What you like to take on the conversion of the tasks to use=20 > config files? >=20 > - Gordon >=20 > -----Original Message----- > From: Raju Bitter [mailto:r.bitter.mailinglists@googlemail.com] > Sent: Wednesday, September 12, 2012 6:41 AM > To: Gordon Smith > Cc: flex-dev@incubator.apache.org > Subject: Is there anything the community can do to help you testing or=20 > documenting Falcon and the build process? >=20 > Gordon, >=20 > It's great to see the Falcon source code contributed to Apache Flex. > Thanks to you and everyone else at Adobe who made that possible. > That's a very valuable contribution! >=20 > Is there anything the community can do to help you with the Falcon code? > Testing the build, updating the documentation in the Wiki? Maybe it=20 > would be good to start working on a Wiki page describing the build=20 > process with Eclipse for Windows, OS X and Linux? I'd volunteer to=20 > help you with that, and I can imagine others would be interested as well? >=20 > - Raju -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui