openrewrite / openrewrite/rewrite
Maven(Clean up) - Remove explicit `compile` scope
Open
Nobody has claimed this yet.
maven
recipe
- Dominant language
- Java
- Stars
- 3.7k
- Forks
- 570
- Avg merge
- 13h 12m
- Merged PRs (30d)
- 261
Description
The compile scope is the default and there is no need to define it explicitly
This is similar to ChangeDependencyScope but that recipe expects a dependency and a scope as the input. We might be able to reuse some of the logic from the visitor
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 rewrite-maven/src/main/java/org/openrewrite/maven/ChangeDependencyScope.java, especially its visitor, to identify reusable dependency-matching logic. Trace the Maven recipe and its tests from there. Done means explicit compile scopes are removed while dependencies retain the default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100