flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject AW: AW: Some Falcon problems with multiple source-paths.
Date Mon, 13 Oct 2014 08:47:48 GMT
Ahem ... I have to admit that I have never compiled Flex without Flexmojos ;-)
But I'll give it a try.

While compiling the Flexicious Ultimate Grid code (I wanted to test with this, cause it uses
all sorts of strange language features and wanted to see how Falcon performs on this) I stumbled
over a problem that we should solve. 

In the Flexicious code some Interfaces are annotated with a "Bindable" metadata (At Interface
Level) ... compiling such an interface causes NPEs in Falcon (IntelliJ even suggests that
this line could throw NPEs) cause in case of a Bindable Interface the class property is never
set. I think we should catch this and add a Warning instead.

I also get some strange OperandStackUnderflowProblem error without any explanation when compiling
these libs.

Think I'll try with some less tricky projects first.


Von: Alex Harui <aharui@adobe.com>
Gesendet: Montag, 13. Oktober 2014 08:33
An: dev@flex.apache.org
Betreff: Re: AW: Some Falcon problems with multiple source-paths.

Can you set up a simple test case that doesn’t require flexmojos that will
reproduce the problem?

On 10/12/14, 11:10 PM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:

>Well I ran Flexmojos twice against the same project. Once with falcon and
>once with the old compiler. Even with the old compiler there was only one
>source-path, but each ressource was added using "include-file"
>declaration and it seemed that the old compiler was able to resolve
>resources from the include-file declarations, and falcon doesn't.
>The two paths are the "source-path" entry itself and the relative path
>directly used in the Embed statement.
>Von: Darrell Loverin <darrell.loverin@gmail.com>
>Gesendet: Montag, 13. Oktober 2014 01:47
>An: dev@flex.apache.org
>Betreff: Re: Some Falcon problems with multiple source-paths.
>The compiler should support multiple source paths. Each "-source-path"
>option defines another source path. The compiler error messages seems to
>say it searched two source paths for the asset. I think you want to add
>your resource path to the source path.
>On Sun, Oct 12, 2014 at 1:24 PM, Christofer Dutz
>> Hi,
>> As I posted two days ago, I have succeeded in getting Flexmojos to work
>> with Falcon. Now while I'm still trying to get the Flexmojos Testsuite
>> running again, I started some first tests with Flexmojos and Falcon
>>where I
>> simply let Falcon compile some of my applications that build fine with
>> old compiler and I just ran into a problem which I could need some
>> In Maven you can have several sources (main-sources, main-resources,
>> test-sources, test-resources for example). Now I have a project in
>>which I
>> have the Flex sourcecode in "src/main/flex" and the resources in
>> "src/main/resources" - which is the default Maven pattern for separating
>> sources and resources. Now when embedding an image, I am getting the
>> following errors:
>> Error: Could not find Embed source '/assets/images/checkboxmiddle.png'.
>> Searched
>> 'assets/images/checkboxmiddle.png' on the source path
>> Which is true, as the resources are not located in the source path but
>> the resource path.
>> would have worked.
>> Having a look at the code to me it seems af if Falcon wouldn't support
>> multiple source roots ... is that correct?
>> Chris

View raw message