Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gosmith@adobe.com designates
 64.18.1.187 as permitted sender)
From: Gordon Smith <gosmith@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Thu, 6 Dec 2012 13:56:17 -0800
Subject: RE: [Falcon] Unit tests failing
Thread-Topic: [Falcon] Unit tests failing
Thread-Index: 
 Ac3TSdyPJcmockSkRG2+OtpzFb8InQAAIXiAAAhXZcEAIgO78AABmFpTAACItHAAAAmzEA==
Message-ID: 
 <149F8129B58B2D418508E63117D9C5419B5B62394A@nambx05.corp.adobe.com>
References: 
 <149F8129B58B2D418508E63117D9C5419B5B62392F@nambx05.corp.adobe.com>
 <CCE6509A.49A15%aharui@adobe.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I should have said Falcon's 'mxmlc' and 'compc' shell scripts.

- Gordon

-----Original Message-----
From: Gordon Smith=20
Sent: Thursday, December 06, 2012 1:55 PM
To: flex-dev@incubator.apache.org
Subject: RE: [Falcon] Unit tests failing

So, how does Falcon's 'asc' shell script do its job? Did you make it use an=
 environment variable to find an SDK?

- Gordon

-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]=20
Sent: Thursday, December 06, 2012 1:40 PM
To: flex-dev@incubator.apache.org
Subject: Re: [Falcon] Unit tests failing


On 12/6/12 12:57 PM, "Gordon Smith" <gosmith@adobe.com> wrote:

> But doesn't it make it impossible to use Falcon's shell scripts, which=20
> expect to find other things in the SDK using relative paths from those=20
> shell scripts???
You mean like the mxmlc and compc scripts?  They take a FLEX_HOME environme=
nt variable and seem to be working.
>=20
> Falcon isn't going to be independent of the SDK in the sense of being=20
> external to it. The goal is for it to replace the old compiler *in*=20
> the SDK. I don't want to be polluting an SDK with Falcon until it is=20
> ready, but it made sense to me to copy whatever SDK you want test=20
> Falcon with into Falcon's directory, so that everything is relative to ea=
ch other as it will eventually be.
>=20
I guess I haven't given up on the vision of Falcon being so independent tha=
t it doesn't have to be in every SDK release.  For sure, I am currently wor=
king on a "new SDK" and I want Falcon and FalconJS to work with it.  I want=
 to finish the vision of not having to change Falcon for every version of t=
he SDK.  That would eventually allow the SDK folder to not contain any java=
 code, and changing SDK versions becomes a matter of changing SWCs and not =
JARs.

And I don't want to eliminate the possibility that someone will take on the=
 effort to integrate Falcon into an IDE.

--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui