build: upgrade to jdk11 -> jdk17 for bundled jre#11693
build: upgrade to jdk11 -> jdk17 for bundled jre#11693offtherailz merged 2 commits intogeosolutions-it:masterfrom
Conversation
There was a problem hiding this comment.
I think that, if we go to Java 17,
- also the documentation should be upgraded accordingly (Suggsted version, consistent with the one used. On master doc for 2026.01 is the max version)
- Build, test runs etc... should run with Java 17. About this, we have this PR that should be merged (first). Anyway this requires all the pending PR to be updated.
For these reason I suggest to
- Update the doc with versions (on this PR)
- wait for PR to be merged <-- for this I suggest to do a recheck of PR pendings immediately after 2025.02.02 release.
P.S. I removed the link to documentation fix because this doesn't fix it, and it refers to another PR. Probably an error @tdipisa
|
Waiting for PR to be merged, Will then rebase with |
Thank you @mahesh-wor. Let's wait for v2025.02.00 to be out next week before merging that. |
@mahesh-wor v2025.02.00 is released. You can now proceed with that. |
|
Hi @tdipisa , seems like the Dockerfile and build stuff is changed from my last PR in |
@mahesh-wor get in touch with brian if you have questions |
321cbfd to
694017a
Compare
|
@offtherailz Hi tested local build with the changes i made, also updated java/jdk recommendation to v17. FYI: We did an upgrade to postgres db version to Postgres 17 for Mapstore2 in this issue, but i see that the |
@mahesh-wor it was purpose of internal https://github.com/geosolutions-it/internal/issues/426 to provide the setup for PGSQL 16 or 17. Therefore, you have to provide all necessary pending changes with a new PR, I suppose. Can you raise it? We have to ensure all is aligned. |
| | npm | [link](https://www.npmjs.com/get-npm) | 8 | 10 | | | ||
| | NodeJS | [link](https://nodejs.org/en/) | 20 | 20 | 25<sup>3</sup> | | ||
| | Java (JDK) | [link](https://www.java.com/en/download/help/develop.html) | 8 | 11 | 17 | | ||
| | Java (JDK) | [link](https://www.java.com/en/download/help/develop.html) | 8 | 17 | 17 | |
There was a problem hiding this comment.
| | Java (JDK) | [link](https://www.java.com/en/download/help/develop.html) | 8 | 17 | 17 | | |
| | Java (JDK) | [link](https://www.java.com/en/download/help/develop.html) | 8 | 17 | 21 | |
There was a problem hiding this comment.
@randomorder and @mahesh-wor
If we are going to use 17 from now on for 2026.01, we should start to use it on dev build / docker / server too, so tests can be done using the suggested version
|
Docker build failed @mahesh-wor . going to reopen the issue. |
Seems like something wrong with If it does not work, will investigate further. |
@offtherailz It's working now, I didn't change a thing. |
Description
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
Earlier the jre bundle was being downloaded from dropbox url for jdk 11.
Apache docker image was using
tomcat:9-jdk11What is the new behavior?
New jdk17 bundle (win/linux) are fetched from https://maven.geo-solutions.it/jdk/17.0.13/
Apache docker image updated to use
tomcat:9-jdk17Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information