And the workaround for
tools.jar works and I can now build again on JamVM
on my rather ancient PowerPC container. At least it works for the most part
Well after awhile it loses track of the compiler, so maybe I should cache it rather than always getting it.
Then it fails because it cannot find the builder class, will need to investigate since it exists within the JAR.
Actually what will be useful is an auto-close after send for large packets such as JAR files.
Since installation can take awhile, I should probably step up the wait time for response packets before the monitor is hit.
The really long imports are a bit of a problem to be honest.
Okay, so I purchased
squirreljme.cc which means that everything
net.multiphasicapps.squirreljme package will be dropped
down to that package:
So this means a 17 character saving! Joy!
The stack traces are like all the way to the left, which is quite something. More screen space saved!