maven: make use of the analyze* goals

[randomicecube]

Was looking at some of mvn's dependency plugin's goals, and analyze (in addition to its variations) seem to have some interesting outputs which we could make use of, namely dependencies which are "used and declared; used and undeclared; unused and declared" -- these last two in particular would be interesting!
There are surely some other aspects of it we can make use of, but these really caught my attention when I saw them.

cc @algomaster99 what do you think?
also, @Stamp9 are you aware of if it's possible to do something similar for the NPM ecosystem?

[algomaster99]

What do yo want to achieve with these goals? Do you intend to list the following three sets:

1. used and declared
2. used and undeclared
3. unused and declared

It seems that maven-dependency-plugin:analyze also wants to compile sources and test-sources which may not be necessary. You could try using https://github.com/ASSERT-KTH/depclean to get all this information.

[randomicecube]

Maybe (probably) not the first one, but yes, the goal was to report on the last two.
I guess we already include DepClean in the README, in the "other issues not handled by dirty-waters" section, so this could be rendered moot?

[algomaster99]

I guess we already include DepClean in the README, in the "other issues not handled by dirty-waters" section, so this could be rendered moot?

If dirty-waters does not intend to report those information, yes, you could close this issue.