Hi Alex,
I could confirm your observation, so in order to test things, I changed the dependencies to all the libraries to the library-path in all cases. With this the output had a lot less errors. However I am still getting errors from the binding system. I am having real trouble to make this setup work nicely in Maven. We seem to have 3 different cases: 1. Library is on library-path for SWC and JS 2. Library is on external-library-path for SWC and JS 3. Library is on external-library-path for SWC and library-path for JS the first two cases are trivial and I select which one by choosing "compile" (1) or "runtime" (2). Unfortunately I have no idea how I could tell maven to use option 3 in a way that is not a complete hack. Would it be ok to add a plugin config option to forcefully link all libraries using external-library-path? Chris ________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Montag, 4. Juli 2016 09:10:22 An: dev@flex.apache.org; Christofer Dutz Betreff: Re: AW: AW: AW: AW: AW: AW: AW: AW: AW: [Falcon][FlexJS] Help with finishing the maven migration On 7/3/16, 7:48 AM, "Alex Harui" <aha...@adobe.com> wrote: >Excellent! I will investigate the runtime issues this evening. I poked around. I noted: -RadioButton is broken. Peter or I will look into it. -For Binding (and probably other projects), Core.swc is on the external-library-path for the AS compile, but needs to be on the library-path for JS compiles. Hopefully that's not too hard to pull off. -I did not see the HTTPService errors. I'll try to find time to look at a few more this week. -Alex
