Support using Gradle projects as the dependency inputs

Open
#1,901 9 comments 2 reactions 0 assignees View on GitHub

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

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.

Description

enhancement

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.

Dominant language
Java
Stars
5.7k
Forks
560
Avg merge
1d 13h
Merged PRs (30d)
43

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from diffplug/spotless

All issues in diffplug/spotless

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.