pareshddevalia opened a new pull request, #646:
URL: https://github.com/apache/atlas/pull/646

   Changes:- Fix the python code, removed unnecessary JPMS and increase the 
stop wait sec
          updated the Readme file
          Refactor deprecated Mockito Matchers to ArgumentMatchers and fix 
failing Hive test cases
          Refactor Mockito imports: remove wildcard and deprecated Matchers 
usage
          Refactor Mockito imports
          Added support for openapi-3.0 for API documentation and fix some 
test-case.
          Bundle commons-text in hbase-hook.
          Fix new test-case for Repository module.
   
   ## 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:
   
   `export MAVEN_OPTS="--add-opens=java.base/java.lang=ALL-UNNAMED \
   --add-opens=java.base/java.lang.reflect=ALL-UNNAMED \
   --add-opens=java.base/java.nio=ALL-UNNAMED \
   --add-opens=java.base/java.net=ALL-UNNAMED "`
   
   Alternatively, you can place these arguments in a .mvn/jvm.config file to 
avoid exporting them manually for every run.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to