e.g. ever picked the wrong clogging pom.xml section and shoved in a dependency on log4j, logkit and avalon on your project? (Its such a shame sun messed up the clogging space btw).
Its way too easy in maven to not really see or care what dependencies you really have, including those transitive ones - and we end up with lots of unnecessary crap. It can be a bit scary to run 'mvn site' then look at dependencies.html to see all the stuff maven's pulling in.
So here's the idea. Its a bit like Jester. When all your tests pass; you run the pom-trimmer; what it does is try removing bits of your pom to see if your tests pass. It tries all the permutations to figure out how much crap it can miss out. (So commenting out
Next though is it should walk the transisitve dependency graphs and find all the transitive dependencies and try avoid those (using
We should try get into the habit of running this before a release so we can all try keep released pom's as free from junk as possible.
So any volunteers to hacking up this little Mojo?