Move to Java 8 requirement? #280
Labels
Comments
This was referenced Oct 8, 2018
|
No objection. Great work with this open source library, @danfickle. Sustain its future with a move to Java 8. |
|
Agreed. Java8 has been out for 4 years. If someone is stuck at jdk 7, they can always use an older release |
|
No problem here - been on Java 8 for a while without incidents. in fact now that J2EE 8 is a thing, I'm looking forward to move to Java 9 (or whatever is the latest version for this week - this new versioning scheme is really awful, thanks Google!) If you're stuck with Java 7, hope you're paying those megabuckos to Oracle for that support contract! |
danfickle
added a commit
that referenced
this issue
Nov 30, 2018
…kip] We now require at least Java 8.
|
RC18 is Java 8 all the way, so closing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We were thinking of moving to a minimum of java 8. This would give us streams/lambdas and other modern goodies. It’s been several years since java 8 was released. If you object, here is your chance to say why.
The text was updated successfully, but these errors were encountered: