Actually I will write a plugin to do such kind of thing, of cause i will create a "ignore list" which contains such as "log4j, commons-logging" we dont care about, the list will be increased with new ingore item add to it.then I will find all the conflict dependency that dont list in the <dependencyManagement> Tag, and throw a exception with full infomations to tell people to manually add it into the dependencyManagement,.
2008/11/17 Geoffrey Wiseman <[EMAIL PROTECTED]> > On Mon, Nov 17, 2008 at 7:47 AM, David Delbecq <[EMAIL PROTECTED]> wrote: > > > This might be what you'r looking for: > > > > > http://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html > > > > Huh - are you suggesting that dependency:analyze will also warn you if, > say, > one dependency's POM declares that it works with commons-collections 1.1.4 > and another's requires commons-collections 1.2.3? > > I don't remember that when I briefly looked at it, but that'd be > interesting > to discover. > - Geoffrey > -- > Geoffrey Wiseman >
