openrewrite / openrewrite/rewrite
wrong maven coordinates for Groovy 4
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.7k
- Forks
- 570
- Avg merge
- 13h 12m
- Merged PRs (30d)
- 261
Description
As of Apache Groovy 4, Groovy aligned its maven coordinates more with the requirements of Apache. Which means that org.apache.groovy is the new namespace and org.codehaus.groovy will not be used anymore for any Groovy version beyond Apache Groovy 3
See for example:
https://mvnrepository.com/artifact/org.apache.groovy/groovy-all/4.0.13
And see
https://github.com/openrewrite/rewrite/blob/c27fcb269be0680e04929b5c015994bbf865bed7/rewrite-groovy/build.gradle.kts#L22 for how the latest version is requested but the namespace still points to Apache Groovy 3.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at rewrite-groovy/build.gradle.kts, especially line 22, and compare the requested Groovy version with its Maven namespace. Check the dependency coordinates against the linked Groovy 4 artifact, then verify that dependency resolution uses org.apache.groovy for Groovy 4 and completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 64/100