I’ve made some pretty major modifications to the build scripts. The
biggest is the move to using dependencies for the libs instead of
bundling them in the source, and doing the same for the server and JRE
The second biggest is creating the lucee-context.lar file on the fly,
instead of manually building it and adding it back to source control.
With those changes, the repo goes from 750+ megs to 12 megs, and
updating the dependencies is a matter of changing version numbers
(including tomcat and whatnot).
The lucee-context.lar “cycle” was adding about 2mb per change. Since it
changes semi-infrequently, it would probably be better to give it it’s
own version number, and build it separately, but at least for now the
whole shebang can be built from scratch, and we’re not repeatedly
putting binary resources under version control. (FWIW, bitbucket
recommends <100mb repos.)
There’s the other nice stuff I’ve talked about too, like checking that
you’re compiling with the right version of java, etc., and a target for
running tests-- including setting up a the test environment, with the
caches and data sources and whatnot set up to run the jira tests, vs.
having to manually set that stuff up to run them.
We’re going to have to do a “synchronize watches” type deal at some
point, as to get rid of the binary artifacts I had to rewrite the
history for the repo, but I wanted to especially toss out the bit about
the lucee-context.lar, and see what the thoughts are about giving it
it’s own version (maybe do the same thing for lucee-inst.jar too, since
it changes infrequently as well).