We won't be able to get rid of all the resulting warnings. So, automating it would probably just encourage people to ignore these warnings instead of address them. I'd rather just make it a point to explicitly check during testing before releasing, and to encourage people to consider dependencies throughout development.
-- Christopher L Tubbs II http://gravatar.com/ctubbsii On Fri, Nov 8, 2013 at 2:29 PM, Mike Drob <[email protected]> wrote: > +1 > > Nobody looks at dependency resolution until it bites you in the rear. > > We could conceivably add this to the pom to automate the running, but would > still need to make sure that somebody reads the output. > > > On Fri, Nov 8, 2013 at 10:37 AM, Billie Rinaldi > <[email protected]>wrote: > >> I would like to add running mvn dependency:analyze as a step in our release >> process. This should be done with both major and minor releases, as it is >> very easy to add new direct dependencies without realizing it (when they >> were previously transitive dependencies), or to leave around dependencies >> that are no longer needed. >> >> Billie >>
