NihalJain opened a new pull request, #142: URL: https://github.com/apache/hbase-thirdparty/pull/142
This change adds a new set of modules which we will need for Jetty 12 migration. The code has been modularised into following modules: - `[hbase-shaded-jetty-12-plus-core](https://issues.apache.org/jira/browse/HBASE-shaded-jetty-12-plus-core)`: Contains shaded jetty 12 core jars - `[hbase-shaded-jetty-12-plus-ee8](https://issues.apache.org/jira/browse/HBASE-shaded-jetty-12-plus-ee8)`: Contains shaded jetty EE8 specific jars So basically: - Branches which want to consume EE8 may need to add `[hbase-shaded-jetty-12-plus-core](https://issues.apache.org/jira/browse/HBASE-shaded-jetty-12-plus-core)` and `[hbase-shaded-jetty-12-plus-ee8](https://issues.apache.org/jira/browse/HBASE-shaded-jetty-12-plus-ee8)` in their dependency replacing the former `[hbase-shaded-jetty](https://issues.apache.org/jira/browse/HBASE-shaded-jetty)` - Branches which want to consume EE9/EE10 may need to add a new module for same in `[hbase-thirdparty](https://issues.apache.org/jira/browse/HBASE-thirdparty)` in future Next, implement maven toolchains-based build system to support both JDK 8 and JDK 17 compilation in a single branch with configurable setup: - Add toolchains plugin configuration for automatic JDK selection - Configure Jetty 12 modules ([hbase-shaded-jetty-12-plus-](https://issues.apache.org/jira/browse/HBASE-shaded-jetty-12-plus-)*) to use JDK 17 - Maintain JDK 8 compatibility for existing modules - Split maven-enforcer-plugin into separate JDK 8/17 bytecode checks - Add generate-toolchains.sh script for dynamic toolchains.xml generation - Support JAVA8_HOME/JAVA17_HOME environment variable configuration - Auto-detect Java installations at /usr/lib/jvm/java-8 and /usr/lib/jvm/java-17 for CI - Force explicit environment variable setup for local development - Remove dependency on ~/.m2/toolchains.xml for project-specific configuration - Add documentation with setup commands and CI/local instructions This allows HBase 2.x to continue using JDK 8 compatible Jetty 9 modules while HBase 3.x can leverage JDK 17 Jetty 12 modules, with seamless Jenkins/CI builds and clear local development setup, eliminating the need for separate branches or releases. WIP: Jenkins change -- 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]
