flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Terry Corbet <terry.cor...@gmail.com>
Subject Re: Falcon unit tests all fail in Eclipse
Date Wed, 03 Apr 2013 04:26:24 GMT
Where, then, can I get a checklist, as of the 4.9.2 release, of which
Flex/AIR/Sparc components we can use with the old mxmlc compiler and which
ones we can use with the new 'ASC2/Falcon' compiler?

If there are any of those components which will never successfully compile
via an MXML declaration and we must therefore instantiate and configure
them with pure ActionScript, the sooner we have such a checklist, the
sooner we will be able to commit to the Apache/Flex SDK instead of
continuing to use the Adobe 4.6 SDK overlaid with each successive Beta
release of AIR 3.x from Adobe Labs.

On Tue, Apr 2, 2013 at 9:01 PM, Gordon Smith <gosmith@adobe.com> wrote:

> Problem solved... I accidentally deleted my unittest.properties file last
> week in a Git mishap. They all pass except for a remaining compilation
> warning in the frameworkSWC() test, which I'll fix.
> - Gordon
> From: Gordon Smith
> Sent: Tuesday, April 02, 2013 8:50 PM
> To: dev@flex.apache.org
> Subject: RE: Falcon unit tests all fail in Eclipse
> Sorry, it's more likely that they've never worked since we've moved to
> Git. I'll figure out why.
> - Gordon
> From: Gordon Smith
> Sent: Tuesday, April 02, 2013 8:46 PM
> To: dev@flex.apache.org<mailto:dev@flex.apache.org>
> Subject: Falcon unit tests all fail in Eclipse
> Not a single unit test for the compiler project passes when run in
> Eclipse. I'm guessing that some change to the Ant scripts has broken them.
> If people are going to make changes to the Falcon build environment, I
> would appreciate it if they would keep the unit tests working in Eclipse,
> because only there can they be debugged.
> - Gordon

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message