"pgier" wrote :
| The easiest way that I know of to find these conflicting dependencies is by using the
dependencies project info report
|
| mvn project-info-reports:dependencies
| It's a pita to go through all the modules and find instances of these conflicts,
but someone (maybe me) should go through the mc modules and fix them.
|
| Another command that can help clean up dependencies is this one:
|
| mvn dependency:analyze
| The report will tell you if you have unused dependencies listed, or if you are
directly dependent on one of your transitive dependencies. When I have time, I plan to
add a feature to this plugin that will tell you if you are including two versions of the
same artifact.
|
These tools should be used before any release anyway.
We need to make sure we are not transitively depending on snapshots
or things we don't want to depend on. e.g. maybe dependning on
alpha/beta version of a project when we do a final release.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080424#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...