Hi, I volunteer to take over the release manager position for 6.x branch. Even for 7.x. I have all JDKs from 1.5.0_22 on and I don't plan to move to different OS anytime soon. On Oct 30, 2015 4:51 PM, "Martijn Dashorst" <[email protected]> wrote:
> While it is just recently that we released Wicket 7 requiring Java7, > the Java eco system is moving along faster than our release schedule > can keep up with. > > I'm sure I won't be able to actually build Wicket 6.x releases next > year due to Java 6 not being available (OS X 10.11 removed the Java 6 > installation I had on my box, I was able to re-install it). It was > damn hard to build it now, thanks to Maven requiring Java 7, and the > need for us to use Java 6 to compile and link the wicket jars. > > Wicket 7 will be similarly hard to build soon because of the JavaDoc > mess Oracle inflicted on us in Java 8, and Java 7 being no longer > publicly available with security updates and such. > > IMO this forces our hand to move quicker with upgrading our minimum > required Java version and perhaps even consider that upgrading the > minimum Java version is not a semver violation. > > WDYT? > > Martijn >
