-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java 7 - no more direct support by the Eclipse CI #2229
Comments
Just to be clear for Californium |
yes. |
At Leshan we use it for a while and nobody complain until now. |
Not sure, if I remember it well, but java 8 introduces "covariant return types". Compiling code using java 8 API jars and just configure the compiler to generate java 7 classes failed then on that functions when executed with java 7. |
I think |
One small downside: |
I missed that because I moved to Java 11 for building when I migrate to |
Currently only "actinium" fails without real "toolchain" (I guess it's more about using oracle java 8 there, than just java 8.) |
using
and the toolchain with oracle java 8 does it for actinium. So, I guess removing the toolchain for californium and californium.tools works, |
Learning from my side: |
Mule CoAP Connector requires java 8 support. No problem to drop java 7 support from there. |
Just to let all know:
Since yesterday, there is no more java 7 support for the CI Jenkins.
If java 7 would be required, that would need a special docker build image.
If using the compiler switch "-release" works, isn't known by me. In that past such similar approaches frequently failed for different reasons and therefore using a jdk 7 via the toolchain was the best option.
Anyway, I don't see, that I'm able to spend my time in overcome that. For Cf 4.0.0 the current plan is anyway to move to at least java 8. So, please try to check the nightly SNAPSHOT build, if that works for you and report, if you have some trouble.
The text was updated successfully, but these errors were encountered: