Warning with maven multi module projects for non-installed dependencies.

Open
#2,947 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
build-system

Research direction

Reproduce the warning in the linked multi-module Maven project using the warning checkout and mvn spotless:apply or mvn spotless:check. Start by tracing the Maven plugin's dependency resolution for expandWildcardImports; done means non-installed dependencies between modules in the same reactor no longer produce the warning when that option is unused.

Written by the indexing model from the issue text.

Description

Given a maven multi module project for which a module depends an another module within the same multi module project and the other module has not been installed, the following warning is issued when doing mvn spotless apply or mvn spotless check (even without the expandWildcardImports option):

[WARNING] Could not resolve project dependencies for expandWildcardImports: Unable to resolve dependencies

To reproduce:

git clone https://github.com/pdeneve/spotless-expand-wildcard-imports-issue.git
cd spotless-expand-wildcard-imports-issue
git checkout warning
mvn spotless:apply

Spotless maven plugin version used = 3.5.1

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.