Is there any need for a Java 7 JSqlParser build, or can we move on to at least Java 8?

Question

Is there any need for a Java 7 JSqlParser build, or can we move on to at least Java 8?

wumpz opened this issue 5 years ago · 6 comments

wumpz commented 5 years ago

cristiker commented 5 years ago

java 8 +1

Answer 1 · 2019-06-30T02:16:07.000Z

+1 on java 8.

Answer 2 · 2019-06-30T06:43:23.000Z

Fine. First comment on this.
I remember an issue not long ago eve Java 6 was mentioned.

I hope the complaints do not start after I switch.

Answer 3 · 2019-06-30T16:41:11.000Z

Well, my consideration was that java 6 wasn’t supported. Java 8 probably loses support for enterprises soon.

I might have been the one that asked about java 6, maybe like 3 years ago :)

There are configurations to produce two artifacts with different jdks from the same maven, but that just adds complications we might not need it no one needs jdk6 or jdk7

Answer 4 · 2019-07-09T08:09:33.000Z

So I will switch and remove Java 7 support with the next release.

Answer 5 · 2019-07-18T06:12:13.000Z

Done. JSqlParser 2.2-SNAPSHOT uses Java 8 at the minimum and is JDK 11 buildable.