Remanufacturing of java+swing complete, and I'm almost done the builds.

I'm working my butt off from the start of the rule changes through
pushing them to the Windows 7 CPU horsepower laptop (16X as fast as
my Linux box), remanufacturing just the java+swing layer, reverting those
script changes, committing and pushing the new code, pulling it down to the
Linux box, rebuilding it in Eclipse, exporting the updated jars, and soon
I'll be redoing the packaging and queueing the results for upload to the
SourceForge servers.  So far I've spent 4 hours on this edit cycle.  I'm
curious as to just how fast I can edit, build, and ship 40+ million lines
of code. :P
CFCore 2.0 can have persistent storage other than RAM, I just
hadn't enabled that functionality because the only thing I use
is the RAM implementation.  But I'm curious to someday see how
fast the engine would run with the back end in an RDBMS instead
of memory.  Just a curiosity thing -- and easily tested when
the time comes -- just plug in a different back and and instantiate
the database.

Note that you really shouldn't *include* CFCore 2.0 as an imported
project.  You should always build against it's libraries instead.
Class extensions are *used* by the manufactured code, so there is no
easy way to shift the code out of a library.