Closed dusan-turajlic closed 3 years ago
I agree! But I still think using the latest LTS is safer.
I can’t say if there are any pros or cons in using java 15 but let's evaluate if we should. A benefit would then be that we would have an easier time upgrading to 17.
But i guess the con is we need to deal with java 15 specific problems.
I’m not for or against either but let's check the current state and what others have experienced before merging.
Ether way great point to bring up 👍
If you are making sure to use the very latest IDEs, frameworks and build tools and starting a greenfield project, you can, without hesitation, use Java 11 (LTS) or even the latest Java 15.
From here
Based on the info there we don't realy gain anything by using Java 15 because we are using kotlin to write the code.
The Java release cycle has become alot more rapid, its now every 6 mounths so the jump from 11 to 17 is not as big as one might think.
But ether way It seems like we can totaly use 15. Maybe we should!
This is a Greengield project and why not use the latest stuff.
It's a risk either way, ether things don't work on 15 and we have to downgrade to 11 or we use 11 and upgrading to 17 is a pain!
IMO, let's just use 15.
Yeah, version 15 sounds good! 👍
Since the backend will be written Kotlin, is the Java version specified here only for the CI process?
@AndreasNasman I updated the Java version and added the a .java-version
to the project so if you use jenv it will automaticly pick up and use Java 15
My main concern is the Java version. I think we should try to use the newest stable version if possible. According to Wikipedia, Java 17 will be LTS in September, and going from 11 to 17 feels like quite a big jump if we later decide to upgrade.