Support Gradle wildcard version or placeholder variable in dependency management recipes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- java
- Domain
- build-system
Research direction
Start at the AddDependency recipe and related dependency management recipes, then trace how version values are interpreted and rendered. Verify the desired behavior by checking that a version such as 1.2.+ is preserved correctly in the resulting added dependency; placeholder support may require separate scope clarification.
Written by the indexing model from the issue text.
Description
What problem are you trying to solve?
My organization regularly wildcards the patch version for projects rather than using an explicit version as it helps to avoid the churn of versioning artifacts explicitly, but we use OpenRewrite to change the versions of several artifacts at once across many repositories. We'd like to have the ability to specify a version of a.b.+ to better support this. We also use placeholders in several locations (i.e. a version of ${dependencyVersion}) which would also be helpful but might be out-of-scope for this issue. I can open another issue for this work if you'd like.
Describe the solution you'd like
When running the AddDependency recipe (or other dependency management recipes), I'd like to be able to specify version: 1.2.+ and have the resulting added dependency be wildcarded properly.
Have you considered any alternatives or workarounds?
A rawVersion property or similar would be just as useful and would allow for wildcarding and for placeholders.
Are you interested in contributing this feature to OpenRewrite?
I'd be interested in contributing but given how busy I am I likely won't be able to work on it anytime soon. I'll update if I find time to work on this.
- Dominant language
- Java
- Stars
- 18
- Forks
- 12
- Avg merge
- 55m
- Merged PRs (30d)
- 28
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from openrewrite/rewrite-java-dependencies
-
recipe
Difficulty 4/5 3-5 days Newbie friendliness 25/100
openrewrite/rewrite-java-dependencies#211 ·
Maintainers usually reply within 1 day
All issues in openrewrite/rewrite-java-dependencies
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws/aws-emulator#30 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 4 days
-
Bug: Minor Status: Triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
GTNewHorizons/GT-New-Horizons-Modpack#27664 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
openrewrite/rewrite#9835 ·
Maintainers usually reply within 1 day
-
serviceability
Difficulty 1/5 Under an hour Newbie friendliness 65/100
OpenLiberty/open-liberty#36348 ·
Maintainers usually reply within 1 day