What about including a single JS file that contains all the code of the module into the SWC? This would even be closer to an SWF (which also contains all code). In Jangaroo packaging, we includ both a single, "minified" file for deployment as well as the tree of non-minified JS files for development / debugging. But I don't know whether the GCC-based build process can produce optimized / minified files per module.
On Mon, Nov 10, 2014 at 9:58 PM, Alex Harui <aha...@adobe.com> wrote: > > > On 11/10/14, 12:43 PM, "Christofer Dutz" <christofer.d...@c-ware.de> > wrote: > > >Yeah ... sorry for that ... I meant SWC containing the SWF, catalog and > >JS resources. > >This way we wouldn't have to switch any maven modules/artifacts for a JS > >build, but simply select FlexJS as compilerName in Flexmojos. > > OK, so in this plan, the SWC would contain the library.swf and catalog.xml > and any other .css and assets, and even asdoc, as well as a tree of .js > files. > > If you have the time to prove it doesn’t break Flash Builder and are > willing to pitch in on getting FalconJX to consume these SWCs it will help > make this the decision we go with. > > -Alex > >
