I'm undecided, so will defer to the rest of the team.
I'm not accustomed to retiring older JDK versions until the bulk of the coders are on versions two levels above it; today most people are on JDK 7 so we recently retired JDK 5, and when most are on JDK 8 then we would retire JDK 6. Tomcat 7, probably our most common target environment, still has a minimum JDK of 6.0 (http://tomcat.apache.org/whichversion.html), so that would be a argument for us to stick with that.
On the other hand, it's important to keep a modern development playground for volunteer developers who can sharpen their skill sets on the latest and greatest technologies while they donate time to our project, we can't and shouldn't attract people if they have to work with older technologies. If some users are stuck with older platforms, they can remain with older versions of JSPWiki until they can upgrade their platforms.
Reading their POMs, both CXF and Camel for their future unreleased versions still have 1.6 as their minimum, on the other hand Apache Solr moved this past March to JDK 7 (http://svn.apache.org/viewvc/lucene/dev/trunk/solr/SYSTEM_REQUIREMENTS.txt?r1=1398570&r2=1457734&diff_format=h). I would say we're about five-six months too early in retiring JDK 6 but it probably wouldn't be a disaster for us if we did it now.
Glen On 07/13/2013 08:01 PM, Ichiro Furusato wrote:
Hi, In my refactoring work I've quickly noted that I've become accustomed to using various JDK 7 features, and with the EOL of JDK 6 back in February just wondering what peoples' thoughts are on bumping up the JDK version of JSPWiki to 1.7, join the Modern Era, etc. If there's no strong reason not to I'll update the pom.xml file to begin using <jdk.version>1.7</jdk.version>, at least for the EntityManager work, which is entailing rather significant changes anyway. Ichiro
