One more thought on this: now that COMPJSC can more or less build its own output instead of relying on COMPC to package its pile of .js files, it might be worth experimenting with combining Falcon and FalconJX so COMPC can produce a SWC or a SWC with JS files based on some configuration parameter. Then there would only be one compiler that produces SWFs or JS based on some -output-type flag.
Thoughts? -Alex On 10/1/16, 10:18 PM, "Alex Harui" <aha...@adobe.com> wrote: >Hi Chris, > >When I read this, I realized I already pushed the changes when I pushed >some other changes yesterday. If the Maven build didn't blow up, it is >probably because it is using its own compile-xx-config.xml files so is >still generating a pile of .js files and packaging them up on the SWF >COMPC run. > >-Alex > >On 10/1/16, 6:10 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: > >>Hi Alex, >> >> >>so I guess ideally this change should be done on a feature branch, so I >>can sort out the Maven issues and we'll merge that back as soon as all is >>working. I would like to ask you to create a "feature-autobuild/"-branch >>for that. Just give me a short note what branch the stuff is in and I'll >>try to sort out the Maven issues. >> >> >>Chris >
