jerryshao opened a new pull request, #9316:
URL: https://github.com/apache/gravitino/pull/9316
### What changes were proposed in this pull request?
Fix the `release` task to avoid JDK version conflicts when running tests.
### Why are the changes needed?
Issue: #8628
The `./gradlew release` command fails because:
- The release task depends on all subproject `build` tasks, which include
running tests
- Some modules (clients, spark-connector, flink-connector, bundles, api,
common) are JDK 8 compatible
- Other modules (server, core, catalogs) require JDK 17
- When tests run during release, there are JDK version conflicts causing
failures
- The workaround `./gradlew release -x test` works but is not ideal
### How was this patch tested?
1. Ran `./gradlew clean` to clean all build artifacts
2. Ran `./gradlew release` successfully (53s, 425 tasks)
3. Verified all 53 module JARs have correct bytecode versions:
- 26 JARs are JDK 8 compatible (bytecode 52.0): clients, connectors,
bundles, api, common
- 27 JARs are JDK 17 (bytecode 61.0): server, core, catalogs,
authorization modules
4. Confirmed the release completes without requiring `-x test`
### Change logs
- Modified release task to depend on `assemble` instead of `build`
- This skips test execution during release to avoid JDK version conflicts
- Tests should be run separately in CI/CD with appropriate JDK configurations
- Added filter to exclude `client-python` which doesn't have an assemble task
- Added comments explaining the rationale
Fixes #8628
--
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]
