As you're ramping up for a 2.0 final, I'd advise to cut the rope at that time for the commander. Versions are cheap, but a pending major version can easily function as the right moment to upgrade to a new base Java version.
I'd suggest not to upgrade the java requirement in a minor version. Martijn On Sun, Dec 4, 2016 at 5:01 PM, Shawn McKinney <[email protected]> wrote: > >> On Dec 4, 2016, at 9:50 AM, Martijn Dashorst <[email protected]> >> wrote: >> >> I've been able to start the Fortress Commander and was able to log in >> using the server Shawn has setup! JAY! >> >> But I ran into the problem that one library requires Java 1.8 >> (jgrapht), and the POM is Java 1.7. >> >> Is it an issue to move Fortress Commander to Java 8? >> >> Java 7 is already end of life, and Java 8 is soon to follow. While not >> a hard requirement, I suggest to keep at least with the minimum >> publicly supported version of Java, which is currently Java 8. > > Yes that’s a known problem where latest jgrapht req’s java 8. > https://issues.apache.org/jira/browse/FC-201 > > The commander works with java 8, (and I agree with your comments about j7 / > end of life) although I didn’t want to force users to j8 due to one lib. > We’ve rolled back to prev version of jgrapht in latest so this app should > work with either version of java. > > Will likely cut the rope on 7 (for good) sometime in the next release or two. > > Thanks, > Shawn > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com
