Skip to content

Commit 2617656

Browse files
authored
Explain which Gradle to use when verifying a Java SDK release (#77004)
1 parent 0bc9e82 commit 2617656

1 file changed

Lines changed: 17 additions & 0 deletions

File tree

‎java-sdk/DEVELOPMENT.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -427,6 +427,23 @@ manager, before sending the vote — should run against the source package in
427427
`gradle/wrapper/gradle-wrapper.properties` to fill in
428428
`<GRADLE-DISTRIBUTION-URL>` and `<GRADLE-DISTRIBUTION-SHA>`.
429429

430+
Run `gradle wrapper` with that same Gradle version. The task configures
431+
`buildSrc`, and a different Gradle resolves a `kotlin-dsl` plugin version that
432+
`verification-metadata.xml` does not pin, so strict verification fails before
433+
the wrapper is written. If your installed Gradle differs, download the pinned
434+
distribution, check it against the same SHA-256, and use it directly:
435+
436+
```bash
437+
curl -LO <GRADLE-DISTRIBUTION-URL>
438+
echo "<GRADLE-DISTRIBUTION-SHA> gradle-<GRADLE-VERSION>-bin.zip" | shasum -a 256 -c
439+
unzip -q gradle-<GRADLE-VERSION>-bin.zip
440+
cd apache-airflow-java-sdk-<VERSION>
441+
../gradle-<GRADLE-VERSION>/bin/gradle build
442+
```
443+
444+
That Gradle version must also support the JDK it runs on; for example,
445+
Gradle 8.14 cannot run on JDK 26.
446+
430447
6. **Staged-binary smoke test.** Resolve the staged Nexus artifacts from a
431448
throwaway project to confirm they're actually consumable, following the
432449
same pattern as the "Dry-run against a local repository" step: point a

0 commit comments

Comments
 (0)