No I'm still quite far from finished with that. I am coming closer and closer, but still I need to do some work. Currently the Core module is not building. Haven't had the time to dig into that though cause I was stuck with merging falcon stuff.
One thing I did notice two days ago, was that I have to compile ASJS with the Flex Tool Group "FlexJS" (that's in falcon-jx) and the externs are compiled using the group "Falcon" (that's in falcon). I would have expected the externs to be compiled using the falcon-jx compiler as the externs belong to the cross compilation tool-chain ... any reason why they don't compile using falcon-jx? Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Samstag, 23. April 2016 18:10 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: [FlexJS] Status on Maven migration Forgot to ask... On 4/23/16, 2:06 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Regarding the double run externc ... I noticed this too ... but I think I >managed to get everything working with just one pass in the Maven build. >In order to get things running I compared the output with the final >output of the Ant JavaScript and re-engineered ALL of the replacement >operations. So eventually looking at the replacements of the maven build >could eliminate the need to run externc twice. OK, I guess I will someday switch to using your replace tools. I've been wondering if there is some other way we should be doing this. Should we just use patch files instead? > >Regarding the merge ... I'm ready when you are. Are you also done with flex-asjs? I haven't looked there at all yet. -Alex
