[
https://issues.apache.org/jira/browse/JENA-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032243#comment-14032243
]
Rob Vesse commented on JENA-714:
--------------------------------
The primary motivator for moving to Java 7 was to stop officially supporting
the end of life Java 6, there wasn't any urgent need for any 1.7 language
features just a desire to nudge users off of Java 6.
Our role as the Jena PMC is primarily of stewarding the community (writing code
is secondary) and my concern is that we would be reneging on a decision we
previously made with the explicit input of the community. That is not to say
that we can't present the idea to the community and revisit the previous
decision.
Also note that the existing decision does not require us to maintain 1.6
language level long term merely for a release or so to allow those in the
community who need more time to move off of Java 6 to complete that transition.
In terms of library compatibility all current dependencies are still 1.6
compatible, again that will change in the longer term as we take dependency
upgrades but right now other than the maven enforcer rules in place there is
nothing stopping someone compiling against Java 6
> Language level upgrade
> ----------------------
>
> Key: JENA-714
> URL: https://issues.apache.org/jira/browse/JENA-714
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Kristian Rosenvold
> Assignee: Andy Seaborne
> Attachments: languageLevel.patch
>
>
> The enclosed patch is a result of running a large number of automated
> language level upgrades available in intellij Idea (about 4000 individual
> items).
> As such, the patch contains no "manual" changes done by hand, and should be
> safe to apply, if somewhat large :)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
