Returning to the topic of Jenkins builds of legacy BoneJ1 for different platforms. What would this BoneJ_.jar used as a basis actually be? Would it be the BoneJ1 JAR as it is now, i.e. the one-in-all that includes plugin code that could be off-loaded such as AnalyzeSkeleton? The JAR also has references to old Java3d / Image3d Viewer code that has serious compatibility issues with Java 8.
Or, would the BoneJ_.jar here be the result of building the mavenized version the legacy code @hinerm and I started at Madison? I'm almost done working out the kinks there. In this version we've offloaded code like Skeletonize to Maven dependencies. Also Java3d code comes now from
org.scijava and Image3D Viewer is a dependency.
This mavenization is going to be my starting point for migrating the code to BoneJ2, but we could take a freeze frame of this code now, and use it to build future bug fixes to legacy BoneJ1. Also some Maven settings like enforcing Java 6 compatibility could be different for it.
At the moment I'm quite confused as to how the BoneJ1 builds are going to actually work in your scenario, but I support the general idea, and see many benefits to it. Could we go over this in more detail, so that we're on the same page, and that I can explain the plan to Michael?