I have merged the ide-projects branch into develop. Now there is a second set of Flash Builder project files to build the SWCs that have JS-specific APIs. I've also updated two of our wiki pages to reflect these changes. [1][2]
-Alex [1] https://cwiki.apache.org/confluence/display/FLEX/FlexJS+Component+Source+Co de+Patterns#FlexJSComponentSourceCodePatterns-JSSWC [2] https://cwiki.apache.org/confluence/display/FLEX/FlexJS+Developer+Setup#Fle xJSDeveloperSetup-AFB On 5/16/16, 10:16 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >But be carefullreverting your branch ... cause this is where I continued >working on the maven build. > >Chris > >________________________________________ >Von: Alex Harui <aha...@adobe.com> >Gesendet: Montag, 16. Mai 2016 20:26:39 >An: dev@flex.apache.org >Betreff: Re: [FalconJX][FlexJS] Changing location of externs SWCs > >On 5/16/16, 11:18 AM, "Harbs" <harbs.li...@gmail.com> wrote: > >>JSC is working, but I doubt it’s that big a deal to change the project >>type definition. >> >>I don’t think we should hold off on changing to a structure which makes >>more sense because of this. > >Well, it isn't so much that the project structure makes more sense or not >that is driving the externs move. It is really about how easy it is to >specify where to find the externs SWCs. By moving them, there is one less >"Linked Resource" to specify in FB, but you still have to specify one that >points to flex-asjs. Since JSC is working in FDT, I guess I'll revert the >move of the externs SWCs. The project structure changes will stay though. > The project structure changes should even help FDT be used to develop the >framework SWCs. > >-Alex >
