docs(contributing): require Groovy 4.x for the JIRA bridge - #1097
docs(contributing): require Groovy 4.x for the JIRA bridge#1097milamberspace wants to merge 1 commit into
Conversation
The JIRA bridge's @grab uses the org.apache.groovy group ID, which only exists from Groovy 4 onward, so it cannot run on Groovy 3.x. Align the install instruction in CONTRIBUTING.md with tools/jira/README.md. Closes apache#1096 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
dpol1
left a comment
dpol1
left a comment
There was a problem hiding this comment.
Approving — the stated minimum was simply wrong, and the fix is grounded: the bridge cannot resolve its dependency on a 3.x runtime.
Verified against the tree
tools/jira/bridge.groovy line 4 grabs org.apache.groovy:groovy-json:4.0.21, and the org.apache.groovy group ID only exists from Groovy 4 onward — Groovy 3 published its modules under org.codehaus.groovy — so @Grab resolution fails outright on a 3.x runtime. tools/jira/README.md (lines 55–56, 81–83) already states the 4.x requirement and the group-ID reason; this brings CONTRIBUTING.md in line with it. A repo-wide grep confirms the changed line was the only remaining "Groovy 3.x" reference, so the sweep is complete.
This review was drafted by an AI-assisted tool and checked and
submitted by an Apache Magpie contributor — not a maintainer, so
a maintainer's review remains the authoritative next step. If
something feels off, please reply on the PR.More on how Apache Magpie handles maintainer review:
CONTRIBUTING.md § Opening a pull request.
2 participants
Summary
CONTRIBUTING.mdtold contributors to install Groovy 3.x or newer, but the JIRA bridge cannot run on 3.x — it requires Groovy 4.x. This bumps the stated minimum to 4.x.tools/jira/bridge.groovyline 4 uses@Grab('org.apache.groovy:groovy-json:4.0.21'). Theorg.apache.groovygroup ID only exists from Groovy 4 onward (Groovy 3 published underorg.codehaus.groovy), so the dependency does not resolve on a 3.x runtime.CONTRIBUTING.mdwithtools/jira/README.md(lines 56, 81–83), which already states the 4.x requirement and the reason. The dashboard generator runs on 3.0+, but since both tools share the same install line, 4.x is the correct minimum to state.Type of change
docs/,README.md,CONTRIBUTING.md)Test plan
prek run --all-filespasses (markdownlint, lychee link check, typos, SPDX — all green on the commit)RFC-AI-0004 compliance
Linked issues
Closes #1096
Notes for reviewers (optional)
Scoped intentionally to the version bump only. A separate, unrelated Groovy scoping bug in
bridge.groovy(top-leveldefconfig vars —TRACKER_URL,API_TOKEN,AUTH_SCHEME— are invisible to thecmd_*methods and raiseMissingPropertyException) was noticed nearby and will be handled in its own issue/PR.