Include stable JS builds in releases

[parente]

Most JS projects release minified, single file copies of libraries for stable releases. To name a few:

• Dojo
• cometd
• jQuery
• RequireJS

We're odd in that we provide the raw source and have scripts people have to run to grab JS dependencies (OpenAjax, cometd), setup a JS build environment (node.js, Rhino, Google Closure, etc.), and then run the build to minify our code. Big hurdle for adoption.

A simple answer would be to do the build of the core coweb code into a coweb.js upon each stable release. We could commit them right into a folder in the repo (e.g., www/libs/build/coweb-0.5.min.js) and then tag the release. Anyone that grabs the stable download will have them. Anyone that clones will have the current raw source plus all the old stable version if they want to use them (e.g., regression testing).

This also simplifies our server setup. People won't have to run scripts to go fetch OAA Hub and cometd anymore. They're baked into the built copy of coweb.js. The downside is now we have other deps in our repo, but they're license friendly and people understand these are builds, not source.

[parente]

0.4 stable build committed along with new NOTICES file and updates to LICENSE to call out third-party code.