Hi,

I'm finishing up changing the way COMPJSC works.  Right now, it generates
a pile of .js files in a folder.  Our build process requires that you then
run COMPC and specify the -include-files option to include that pile of
.js files into a final SWC.

This is insufficient for IDE users.  If you create a FlexJS Library
project, an IDE like FlashBuilder will compile the source into a SWC on
every build.  You can then go and run the COMPJSC script and generate the
pile of .js files, but then you have to force the SWC to build again so it
will pick up the .js files.  Plus you have to specify the .js files to
include in the project settings.

The proposed change is that COMPJSC can be given the same -output
parameter as COMPC and COMPJSC will inject the .js files directly into the
SWC.  This will eliminate the step of having to force the build of the SWC
after .js files are generated.  And it will mean that the resulting SWC
can be deployed to other developers on the team.

This change will require a change to the Ant build script.  Currently the
Ant build script calls COMPJSC first, then COMPC.  I am going to flip the
order because COMPJSC now expects a SWC to exist in order to stuff.  What
do we have to change in the Maven build to flip the order as well?

Thanks,
-Alex


Reply via email to