For xml do you mean the js build instead of externc?

Afaik the config xml files are used as is so ide can use them.

Sent from my LG G3, an AT&T 4G LTE smartphone

------ Original message------
From: Christofer Dutz
Date: Fri, Jun 17, 2016 9:01 AM
To: dev@flex.apache.org;
Subject:AW: AW: [FlexJS][Maven] Comparing Maven and Ant output

Ok ... so far it seems almost all modules in the Framework compile. The only 
problem I am having with, is the XML module, I'm strangely getting tons of 
errors from this during the externc compilation. When looking into this, I 
noticed quite some changes in the way the config is loaded. Eventually I have 
to extend the maven plugin to use a default template and to allow specifying a 
"configuration" which changes the template which is used, but we would have to 
keep these in sync with the config-xml in the FDKs framework directory. 
Eventually I should invent something that packs all the config variants into 
one jar that the flexjs-maven-plugin could reference. The downside would be yet 
another cycle from asjs --> falcon --> asjs ... would it be possible to create 
a module in falcon with the config xmls and to unpack that when building the 
FDK with Ant?


Am I correct that now there is a config-xml in each project but this is now 
used as some sort of overlay over some templates from the FDK framework 
directory? But it seems as if this is currently only used for the externs ... 
is that correct?


Chris

________________________________
Von: Alex Harui <aha...@adobe.com>
Gesendet: Dienstag, 7. Juni 2016 17:30:32
An: dev@flex.apache.org
Betreff: Re: AW: [FlexJS][Maven] Comparing Maven and Ant output



On 6/7/16, 5:35 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:

>Ok ... this is a tricky task [?]
>
>
>So I finally have all the externs in the falcon codebase produce
>semantically identical catalog.xml (and hence hopefully identical swcs).
>Today I managed to finish the asjs/framework/project libs too

Sounds like great news!

>Here I'm only having problems with the flat library as the resulting swc
>doesn't reference the components from the HTML swc as part of the
>namespace.

There is an -include-lookup-only option that you need to add to the Flat
compile.

>
>So now I'll start comparing the extern/js swcs ...

Not sure how you are doing the comparison, but you could also gamble and
start building and running the examples and see what is broken.

Thanks,
-Alex

Reply via email to