Hi,
I've been working to overhaul the build system to phase out the custom
JavaScript build script in favor of Ant. I'm currently writing a blog
post about the full process leading up to this, but suffice it to say
that I now have an Ant script working that has most of the functionality
of the original build script. A big advantage to using Ant instead of
the custom build script is that it is now possible to create two
important release artifacts:
1. A minimized JavaScript file which contains all of the JavaScript
modules in scxml-js
2. A class file and JAR version of scxml-js that can be run standalone
on the JVM
The first artifact means that only one JavaScript file will need to be
downloaded to a web page for scxml-js to compile SCXML documents on the
fly, while the second artifact means that the user will only need to
download a single JAR file in order to run scxml-js from the command line.
Using ant also means that it will be possible to integrate the building
of these artifacts with the test code that is already in place, so the
built artifacts will be tested to ensure their robustness.
Once this is complete, I think it should be technically feasible to roll
out a (super pre-alpha) release suitable for end users, comprised of
these two artifacts.
What I'm wondering is whether there is anything I need to do (in terms
of licensing, etc.) in order to publish a release?
Let me know what you think. Thanks,
Jake
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
