Hi Alex,
you were right ... the strange thing was that I looked at your "this instead of
that" and couldn't notice the difference. Had to look at it 3 or 4 times to
notice the missing "3" ... gee ... I seem to be blind for the details.
Just to quote a German saying: "As soon as you start doing it right, it starts
working" ;-)
I also added the -include-lookup-only to the config options of the maven plugin
and now the Flat project also produces the correct output in the catalog.xml.
Now I'm down to some examples not compiling ... but I'll try to sort this out
on my own first ...
Chris
________________________________
Von: Alex Harui <aha...@adobe.com>
Gesendet: Mittwoch, 8. Juni 2016 18:09:26
An: dev@flex.apache.org
Betreff: Re: AW: [Falcon] Declaring defines in config xml doesn't seem to work
On 6/8/16, 8:46 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Hi Alex,
>
>
>could it be possible that it doesn't work when doing the
>"js-compilation"? I added this to the compile-js-config.xml:
The cross-compile is also using compile-js-config and is working for me.
>
> <define>
> <name>COMPILE::JS</name>
> <value>true</value>
> </define>
> <define>
> <name>COMPILE::AS</name>
> <value>false</value>
> </define>
></compiler>
>
>But I get:
>
>Can not resolve config constant: 'AS3'
>COMPILE::AS3
>^
>
>So eventually it works in falcon itself, but doesn't in the FlexJS
>compiler?
>
Well, could it be that you have:
<name>COMPILE::AS</name>
instead of:
<name>COMPILE::AS3</name>
-Alex
