-
Notifications
You must be signed in to change notification settings - Fork 672
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
Bump min java version to 1.8 #1218
Comments
I vote against it. I wouldn't want to force Java 8 as a requirement on users of Gitblit. Not just so that it can use the latest versions of whatever dependencies it has without reason. While there is merit in keeping up-to-date with dependencies, there should still be a good reason why an update is done, if the system currently is working. So updating all dependencies just because, and thereby stepping up the Java requirement, is not a good idea, I think. |
I vote for java 8 as a minimal version. Java 9 is already released and Java 7 reached its public end of life long time ago. I just ran an OWASP-dependeny check against GitBlit source and the result was... improvable. From a security point of view, it would be good to have the chance to update to patched versions of dependencies. Stability could be ensured by raising test coverage... and maybe beta/milestone releases? |
Given the time between releases, I vote for Java11. It is the actual LTS. Java 8 would have been an option 3 years ago. |
Voting for JDK 8 also. It is harder and harder to set-up build environment to use jdk7. Recently You must even keep two versions of ANT as only up to 1.9 allows to use pre 8 JDK what can be a real mess up. |
Voting for Java 11. |
From Gitblit version 1.10.0 on the minimum Java version is Java 8. |
We should bump the min java version to 1.8 in the next release so we can bump jetty version and other deps and other deps which requires java 1.8+.
The text was updated successfully, but these errors were encountered: