[elharo]

No description provided.

[gnodet]

Should we enable maven-dependency-analyzer with failOnUnusedDeclaredDependencies and failOnWarning
in some parent ?

[elharo]

Probably not yet. That would break a lot of other plugins that haven't been cleaned up yet.

[gnodet]

Probably not yet. That would break a lot of other plugins that haven't been cleaned up yet.

That would break plugins only when upgrading the parent. The exact point is to enforce new plugin releases to have clean dependencies. Anyway, not a big deal...

[elharo]

Yes, that's true. It's still a lot of extra work to do before updating the parent, which might need to be done quickly for unrelated reasons.

[gnodet]

Yes, that's true. It's still a lot of extra work to do before updating the parent, which might need to be done quickly for unrelated reasons.

Given the m-dependency-p's analyze goal knows about direct dependencies, why don't we have a goal to automatically fix these dependencies, i.e. remove unused ones and add undeclared ones. Even if that's not perfect, it could still be tuned by the user, but it would remove a big part of the tedious work.

[elharo]

I've probably got the analyzer to the point where adding used undeclared dependencies makes sense. Removing "unused" dependencies is trickier since so many of those are loaded by reflection, service providers, or other mechanisms that the analyzer doesn't see. But sure, go ahead and file a feature request on maven-dependency-plugin Jira.

Meanwhile can we merge this PR?