unusedCompileDependencies doesn't play well with grouped dependencies

[JD557]

I have a project using pureconfig via "com.github.pureconfig" %% "pureconfig" % "0.12.0"

If you look at the build.sbt, you'll notice that this artifact simply bundles pureconfig-core and pureconfig-generic.

Due to this, running undeclaredCompileDependencies always returns pureconfig-core/pureconfig-generic and running unusedCompileDependencies always returns pureconfig.

Unfortunately, this means that simply running unusedCompileDependencies can point to dependencies that are actually being used, so it can't be safely used without fixing the undeclaredCompileDependencies first.

Is this the expected behavior?

[cb372]

Hi! Sorry for the slow response.

I'm afraid this is the expected behaviour. Technically you are declaring a dependency on one artifact (pureconfig) but your code is actually depending on its transitive dependencies.

You have two options to work around this:

• Change your libraryDependencies to depend directly on pureconfig-core and pureconfig-generic. This is not a great option - you shouldn't have to change your build config just to satisfy the plugin
• Add filters to tell the plugin to ignore pureconfig (see the README

It would be nice to handle cases like this automatically, but I can't think of a reliable heuristic we could use to detect it.