Bump the JDK requirement for build time from JDK 8 to JDK 17
envgap__apache__shardingsphere-elasticjob-2509
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
674ff4f63da64595a5350172ffc3ea9c7398b749- Manifest
pom.xml- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
apache/shardingsphere-elasticjob #2509 · read the original issue
## Feature Request **For English only**, other languages will not accept. Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot make decision by current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Is your feature request related to a problem? ### Describe the feature you would like. - For scenarios like https://github.com/apache/shardingsphere-elasticjob/pull/2508 , it is necessary to bump the JDK requirement during the build process from JDK 8 to JDK 17 in order to use Spring Boot 4 classes in logic classes and unit test classes. - This is similar to the process mentioned in https://github.com/apache/shardingsphere/issues/37884 . However, since the new module requires JDK 17 as the runtime, it seems there will always be Maven modules that require JDK 17 as the minimum JDK runtime requirement. Of course, existing modules can still use JDK 8 as the JDK runtime.
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]