ATLAS-5002 : Support Java 17 for build and runtime#409
Closed
pareshddevalia wants to merge 13 commits into
Closed
Conversation
mneethiraj
approved these changes
Jul 23, 2025
pareshddevalia
force-pushed
the
ATLAS-5002
branch
from
4cae064 to
25ec835
Compare
pareshddevalia
force-pushed
the
ATLAS-5002
branch
from
25ec835 to
6e6f303
Compare
pareshddevalia
force-pushed
the
ATLAS-5002
branch
4 times, most recently
from
e11a9cc to
21b1061
Compare
pareshddevalia
force-pushed
the
ATLAS-5002
branch
from
4c817b1 to
0dbb09a
Compare
pareshddevalia
force-pushed
the
ATLAS-5002
branch
from
01656a4 to
4035cc1
Compare
|
Any updates on this, are we getting this? |
pareshddevalia
force-pushed
the
ATLAS-5002
branch
from
4035cc1 to
8fe18d6
Compare
Contributor
Author
Yes, we are in process of review state. |
pareshddevalia
force-pushed
the
ATLAS-5002
branch
5 times, most recently
from
a2ac51a to
6922bdf
Compare
# Conflicts: # .github/workflows/ci.yml # notification/src/test/java/org/apache/atlas/notification/RestNotificationTest.java
…ing Hive test cases
…fix some test-case.
pareshddevalia
force-pushed
the
ATLAS-5002
branch
from
22b57ea to
4c97fc4
Compare
1) commons-configuration2 in coprocessor without commons-text.jar on plugin CP java.lang.NoClassDefFoundError: org/apache/commons/text/lookup/StringLookupFactory at org.apache.commons.configuration2.interpol.DefaultLookups.<clinit>(...) Caused by: java.lang.ClassNotFoundException: org.apache.commons.text.lookup.StringLookupFactory at org.apache.atlas.plugin.classloader.AtlasPluginClassLoader$MyClassLoader.findClass(...) Also surfaced as: The coprocessor org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor threw java.lang.InstantiationException: org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor
pareshddevalia
force-pushed
the
ATLAS-5002
branch
from
3d016ea to
49368ae
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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?
This PR introduces support for Java 17 across both build and runtime environments, while retaining compatibility with Java 8. The system can now be built and executed seamlessly using either JDK 8 or JDK 17.
How was this patch tested?
The patch was validated on both JDK 8 and JDK 17 through full Maven build cycles and runtime execution.
Maven Build Verification
JDK 8:
mvn clean install
JDK 17:
mvn clean install
Scenario 1: JDK 8 Build and Runtime
Scenario 2: JDK 8 Build and JDK 17 Runtime
Scenario 3: JDK 17 Build and Runtime
Note for JDK 17 Users:
Running integration tests (especially Jetty server-based tests) with JDK 17 requires additional JVM arguments due to stricter module access. These can be provided via MAVEN_OPTS:
Alternatively, you can place these arguments in a .mvn/jvm.config file to avoid exporting them manually for every run.