Skip to content
This repository has been archived by the owner on Jan 11, 2024. It is now read-only.

Java 8 #203

Closed
natdan opened this issue Jan 2, 2016 · 3 comments
Closed

Java 8 #203

natdan opened this issue Jan 2, 2016 · 3 comments

Comments

@natdan
Copy link
Contributor

natdan commented Jan 2, 2016

Is there any reason why pi4j should be Java 1.7 bound?

@savageautomate
Copy link
Member

Traditionally for a library, I try to maintain one major version older than the currently released JVM. So many tools and containers take a while to update to the latest JVM and just did not want it to be an obstacle when using Pi4J.

Maybe with Java 8 now shipping on the Pi its time to consider updating?

Thanks, Robert

@natdan
Copy link
Contributor Author

natdan commented Jan 11, 2016

Completely agree. Only difference now is that Java 8 brings quite a lot of new stuff directly applicable to many aspects of pi4j (namely closure/lambdas) and we're already on update #65.

This is quite deliberately open question here so everyone can jump in and agree or oppose move. I am not in hurry to just jump the train and leave wreckage behind (incompatible code breakage, etc).

But, if nobody objects - why not? Any comments?

@savageautomate
Copy link
Member

Updated min requirement to Java 8 in version 1.2-SNAPSHOT
Via commit: 51c1e9a

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants