Support using Gradle projects as the dependency inputs
- Dominant language
- Java
- Stars
- 5.7k
- Forks
- 561
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 43
Description
I'd finished Ktlint custom rule sets support in #1896, but it supports Maven coordinates only due to the limits of
https://github.com/diffplug/spotless/blob/0189f717ee13acdb00745bffa86c6ed4ede53ef2/lib/src/main/java/com/diffplug/spotless/JarState.java#L56-L59
We can extend this for Gradle local projects to be used as the inputs, not sure if this way works for Maven projects as well.
Contributor guide
Research direction
Read lib/src/main/java/com/diffplug/spotless/JarState.java at lines 56-59 and review the Ktlint custom rule set work in #1896. Trace how Maven coordinates currently become dependency inputs, then determine how a Gradle local project can provide the same input. Done means Gradle projects are accepted as inputs while the existing Maven-coordinate path remains usable.
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