You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2024. It is now read-only.
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?
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).
Is there any reason why pi4j should be Java 1.7 bound?
The text was updated successfully, but these errors were encountered: