I don't know how to change the default debug config.

However, running 'ant copy.sdk' makes it work just fine. So 'ant eclipse' 
should do 'ant copy.sdk'.

- Gordon

-----Original Message-----
From: Alex Harui [mailto:aha...@adobe.com] 
Sent: Friday, December 07, 2012 3:49 PM
To: flex-dev@incubator.apache.org
Subject: Re: [Falcon] Unit tests failing

Sounds good to me.  But where does the default debug configuration get 
established?  Where in Eclipse do I go to set it up?  Or what file can I change 
elsewhere?


On 12/7/12 3:45 PM, "Gordon Smith" <gosm...@adobe.com> wrote:

> All unit tests (at least for Falcon) should be zero-configuration. You 
> open up a file like MXMLArrayTagTests.java. You double-click the name 
> of an individual test you want to debug, such as the first one, 
> MXMLArrayTag_empty(), to select it. Then you right-click on it and 
> choose Debug As > JUnit Test from the context menu. It should just 
> work. The default debug configuration that gets created for this test 
> needs to be sufficient without any additional Program Arguments or VM 
> Arguments.
> 
> - Gordon
> 
> -----Original Message-----
> From: Alex Harui [mailto:aha...@adobe.com]
> Sent: Friday, December 07, 2012 3:36 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: [Falcon] Unit tests failing
> 
> The copy.sdk target is still in there if you need it.
> 
> But first, wow do you use the unit tests from Eclipse?  I've never 
> tried it, I always use the command line.  Do you set up a run config 
> of some sort?  If you set a FLEX_HOME in the config's environment does that 
> work?
> 
> Once I understand how you use Eclipse I will try to get it to work.
> 
> 
> On 12/7/12 3:27 PM, "Gordon Smith" <gosm...@adobe.com> wrote:
> 
>> After trying and failing to do any Falcon work today, I'll keep 
>> complaining about this. The unit tests are no longer working in 
>> Eclipse. I get
>> 
>> command line
>> Error: unable to open
>> 'D:\Apache\incubator\flex\falcon\trunk\compiler\generated\dist\sdk\fr
>> a
>> meworks\
>> mxml-2009-manifest.xml'.
>> 
>> command line
>> Error: unable to open
>> 'D:\Apache\incubator\flex\falcon\trunk\compiler\generated\dist\sdk\fr
>> a
>> meworks\
>> libs\player\11.1\playerglobal.swc'.
>> 
>> This is presumably because the SDK is no longer being copied into a 
>> place that the unit tests can find them. The unit tests can't use an 
>> environment variable to find them because it is infeasible to specify 
>> that environment every time you want to make an Eclipse debug config 
>> for a particular unit test.
>> 
>> Is there some way to make this work in Eclipse that I don't know 
>> about, so that every JUnit test "just work" without having to 
>> customize a run-config or debug-config for it?
>> 
>> If not, I will restore some ant targets to do the SDK copying. Alex 
>> may not want to use them, but I need to.
>> 
>> - Gordon
>> 
>> 
>> -----Original Message-----
>> From: Gordon Smith
>> Sent: Thursday, December 06, 2012 2:58 PM
>> To: flex-dev@incubator.apache.org
>> Subject: RE: [Falcon] Unit tests failing
>> 
>> OK, then I'll stop complaining.
>> 
>> - Gordon
>> 
>> -----Original Message-----
>> From: Alex Harui [mailto:aha...@adobe.com]
>> Sent: Thursday, December 06, 2012 1:59 PM
>> To: flex-dev@incubator.apache.org
>> Subject: Re: [Falcon] Unit tests failing
>> 
>> The versions in compiler/commandline already looked for FLEX_HOME 
>> environment variable.
>> 
>> 
>> On 12/6/12 1:56 PM, "Gordon Smith" <gosm...@adobe.com> wrote:
>> 
>>> I should have said Falcon's 'mxmlc' and 'compc' shell scripts.
>>> 
>>> - Gordon
>>> 
>>> -----Original Message-----
>>> From: Gordon Smith
>>> 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:aha...@adobe.com]
>>> 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" <gosm...@adobe.com> wrote:
>>> 
>>>> But doesn't it make it impossible to use Falcon's shell scripts, 
>>>> which expect to find other things in the SDK using relative paths 
>>>> from those shell scripts???
>>> You mean like the mxmlc and compc scripts?  They take a FLEX_HOME 
>>> environment variable and seem to be working.
>>>> 
>>>> Falcon isn't going to be independent of the SDK in the sense of 
>>>> being external to it. The goal is for it to replace the old 
>>>> compiler
>>>> *in* the SDK. I don't want to be polluting an SDK with Falcon until 
>>>> it is ready, but it made sense to me to copy whatever SDK you want 
>>>> test Falcon with into Falcon's directory, so that everything is 
>>>> relative to each other as it will eventually be.
>>>> 
>>> I guess I haven't given up on the vision of Falcon being so 
>>> independent that it doesn't have to be in every SDK release.  For 
>>> sure, I am currently working 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 the 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
>>> 
>> 
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>> 
> 
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
> 

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

Reply via email to