Skip to content

RANGER-4076: Support Java 17 for build and runtime#872

Open
pradeepagrawal8184 wants to merge 11 commits intomasterfrom
RANGER-4076_master
Open

RANGER-4076: Support Java 17 for build and runtime#872
pradeepagrawal8184 wants to merge 11 commits intomasterfrom
RANGER-4076_master

Conversation

@pradeepagrawal8184
Copy link
Copy Markdown
Contributor

What changes were proposed in this pull request?

Support jdk17 build in Ranger. This change shall discontinue build support on jdk8/11

How was this patch tested?

Manual install, start and crud operations on the policy, group, users, service etc.

@kumaab
Copy link
Copy Markdown
Contributor

kumaab commented Apr 1, 2026

Thanks @pradeepagrawal8184 for this patch, I think it is best to update the CI/CD build in this PR by removing builds for JDK8 and JDK11 and adding support for JDK17.

The jobs build-8 and build-11 can be removed from https://github.com/apache/ranger/blob/master/.github/workflows/ci.yml and a similar one for build-17 can be added, the docker builds don't require changes.

Comment thread credentialbuilder/pom.xml Outdated
@pradeepagrawal8184
Copy link
Copy Markdown
Contributor Author

Current ranger master branch shipped jars vs jar shipped with this branch changes.
ranger-master-jars.txt
ranger-4076-jars.txt

@pradeepagrawal8184 pradeepagrawal8184 force-pushed the RANGER-4076_master branch 3 times, most recently from e7cd2ea to 9f9247c Compare April 6, 2026 06:36
@ramackri
Copy link
Copy Markdown
Contributor

ramackri commented Apr 6, 2026

Hi @pradeepagrawal8184,
As part of the JDK 17 upgrade, are we planning to migrate from Spring 5.x to Spring 6.x as well, or will the Spring upgrade be handled separately after this PR is merged?
We’ve observed that several CVE issues are addressed in Spring 6.x, so wanted to understand the plan.
cc >> @mneethiraj

@pradeepagrawal8184
Copy link
Copy Markdown
Contributor Author

Hi @pradeepagrawal8184, As part of the JDK 17 upgrade, are we planning to migrate from Spring 5.x to Spring 6.x as well, or will the Spring upgrade be handled separately after this PR is merged? We’ve observed that several CVE issues are addressed in Spring 6.x, so wanted to understand the plan. cc >> @mneethiraj

@ramackri : Spring upgrade can be handled separately. We can discuss that in the spring upgrade ticket after this PR merge and decide.

Copy link
Copy Markdown
Contributor

@kumaab kumaab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've reviewed the changes partially (since this is a big patch), some JWT related functionalities recently added seems to have been removed, please rebase and take a look. thanks.

@pradeepagrawal8184 pradeepagrawal8184 force-pushed the RANGER-4076_master branch 3 times, most recently from 890fc0a to 32469c3 Compare April 12, 2026 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants