On 5/2/16, 9:26 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>I wasn't planning a release fire ApacheCon. Hmm. I guess I misinterpreted your past emails. I will lower the priority and go back to other things. >I know a lot more work has to be put into this and it's not realistic to >have something in a release state. Eventually ApacheCon EU will be a >better platform for that. I hope it doesn't take us until September/October to do Maven. FWIW, I was thinking about creating separate projects for the externs SWC in FlexJS. Right now we have: Frameworks/projects/Core Frameworks/projects/HTML Frameworks/libs Frameworks/externs Each of the frameworks/projects contains a Flash Builder project. But it is not easy to get that one project to produce both the externs SWC and the regular SWC, and it sounds like Maven doesn't like it either. So, what if we added an externs tree, something like this: Frameworks/projects/Core Frameworks/projects/HTML Frameworks/libs Externs/projects/Core Externs/projects/HTML Externs/libs The externs projects would have no source code. Their source-paths would use ../../../frameworks/projects/XXX to reach around and share the code. Thoughts? -Alex
