Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Apparently despite me changing my JDK locally on the project itself, once pushed to Heroku, the application was still being built and compiled using JDK 1.8. To solve the issue, I included a syste...
Answer
#2: Post edited
by
cuzzo
·
2022-01-06T23:55:27Z (almost 3 years ago)
Apparently despite me changing my JDK on the project itself, once pushed to Heroku, the application was still being built and compiled using JDK 1.8.- To solve the issue, I included a system.properties file in the project directory with:
- `java.runtime.version=14` for JDK 14
- Apparently despite me changing my JDK locally on the project itself, once pushed to Heroku, the application was still being built and compiled using JDK 1.8.
- To solve the issue, I included a system.properties file in the project directory with:
- `java.runtime.version=14` for JDK 14
#1: Initial revision
by
cuzzo
·
2022-01-06T23:54:59Z (almost 3 years ago)
Apparently despite me changing my JDK on the project itself, once pushed to Heroku, the application was still being built and compiled using JDK 1.8. To solve the issue, I included a system.properties file in the project directory with: `java.runtime.version=14` for JDK 14