openrewrite / openrewrite/rewrite
Support updating Gradle programmatic Version Catalogs
Open
Nobody has claimed this yet.
enhancement
gradle
- Dominant language
- Java
- Stars
- 3.7k
- Forks
- 571
- Avg merge
- 13h 12m
- Merged PRs (30d)
- 261
Description
What problem are you trying to solve?
Enable updating of version catalogs defined within settings.gradle scripts.
Describe the solution you'd like
I think either of the following would be a reasonable solution:
UpgradeDependencyVersionandUpgradePluginVersionalso handle programmatic version catalog updates- New recipes to perform these updates
Have you considered any alternatives or workarounds?
None exist right now without a user crafting a custom recipe.
Additional context
- Originally asked for in https://github.com/openrewrite/rewrite/issues/4400#issuecomment-2421723868
Are you interested in contributing this feature to OpenRewrite?
Always. :)
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 by reading the UpgradeDependencyVersion and UpgradePluginVersion recipes in the rewrite repository, then trace how they identify version catalogs. Check how settings.gradle scripts are represented and find related recipe tests. Done means programmatic version catalogs can be updated through the existing recipes or clearly scoped new recipes, with tests covering the requested updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100