Not sure whether this can go into 3.3.3 or not, but my plans are:
-
polish the maven story, the next step that converts to a multi-module project is already in a PR, further steps would be to research what exactly is needed to upload the Vassal jar to maven central. This would mean some additional work for you Joel, you would have to create an account at this sonatype nexus server, a set of gpg keys to sign the releases with, possibly more.
-
look into using jpackage and how we could get Travis configured to build on the three different OSes, there is a very interesting project here github.com/dlemmermann/JPackage … agefx-main that builds jpackage’d releases on different OSes, and Travis offers what they call “matrix builds” that build once on each of the three OSes. This could potentially allow us to build final releases on the CI server.
-
this here did sound pretty interesting https://forum.vassalengine.org/t/cpu-profiling/10728/1, Joel you think you can dig out what you did there? Just send me the patch if you’re too busy and I’ll take care of packaging it up in a nice PR. Otherwise I’ll just see about implementing the changes that Brent proposed.
-
work on removing the last calls to closeQuietly(), if it’s too tricky I’ll just write a new closeVerbosely() that tries to close and writes possible exceptions into log.error()
-
work on cleaning up formatting issues
-
work on removing compile warnings