feat: Retarget Ant build to JDK 21 (no code changes) - #1
feat: Retarget Ant build to JDK 21 (no code changes)#1devin-ai-integration[bot] wants to merge 2 commits into
Conversation
Original prompt from Jake
|
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Note: Filling out this template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the
maintainer's discretion.
Description of the Change
Retargets the fork's Ant/NetBeans/Travis build configuration from Java 11 to Java 21 LTS without changing production or test source code.
Changed files:
release-build.properties:worldwind.jdk=11→worldwind.jdk=21nbproject/project.properties:javac.source/javac.target11→21.travis.yml:openjdk11→openjdk21release-build.xml: Javadoc standard API link updated from Java 8 HTTP docs to Java 21 HTTPS docsDiff summary:
Baseline metrics captured separately before changes on
developcommit2543c234349c76f4a290e318b49f071ac156d2a0under JDK 11:Build/test verification:
Note: both JDK 11 and JDK 21 builds emit the existing external Javadoc warning for the JogAmp URL (
https://jogamp.org/deployment/v2.4.0-rc-20200307/javadoc/package-list) but continue toBUILD SUCCESSFUL.Rationale: Java 21 is the current LTS target and this foundation PR isolates build retargeting from source modernization. Keeping this PR free of source/test edits makes it a clean compatibility gate for follow-on package-scoped modernization PRs.
Devin session: https://app.devin.ai/sessions/36287b7c637242dba0a6a659737d5402
Why Should This Be In Core?
This establishes Java 21 as the build/test baseline for the fork while preserving the existing WorldWind Java API and implementation unchanged.
Benefits
Potential Drawbacks
Applicable Issues
N/A
Requested by: @jakexcosme
Devin Review