RANGER-4076: Support Java 17 for build and runtime #403
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Added support for Java 17 in both build and runtime environments, alongside support for Java 8.
How was this patch tested?
This patch has been successfully tested and verified with Java versions 8, 11, and 17. The verification process included both manual and Docker setup. Now we are able to build and run on same jdk.
JDK 8 maven build successfully with Test-cases
mvn clean compile package install
JDK 11 maven build successfully with Test-cases
mvn clean compile package install
JDK 17 maven build successfully with Test-cases
mvn clean compile package install -Pranger-all-modules-jdk17
Validated policy enforcement for below scenario :
Scenario 1:
Successfully validated usersync, tagsync and policy enforcement(policy-condition) for HDFS, HBase and Hive services using Ranger with JDK 8 for both build and runtime environments.
Scenario 2:
Successfully validated usersync, tagsync and policy enforcement(policy-condition) for HDFS, HBase services using Ranger with JDK 17 for both build and runtime environments.