"pgier" wrote : "adrian(a)jboss.org" wrote : | | | | It certainly allows you to be very explict about what you want and understand | | what your real dependencies are. :-) | | | | e.g. I don't care that JBossXB defines apache-xxx:1.2.3, I want to use apache-xxx:2.3.4 | | Currently I don't even know that it using it at all without some nontrivial investigation. ;-) | | If you define apache-xxx:2.3.4 as a direct dependency,it should be using that one. | | We had some problems with microcontainer in the past because the dependency's groupId changed, so maven didn't know they were the same dep, and that caused the older one to be used. It still doesn't unless you exclude versions from transitives which takes some effort (e.g. the -X flag to figure out where versions are really coming from). anonymous wrote : | You can also use the project info report | mvn project-info-reports:dependencies | | And that should show what your project is actually using. | Yes, that looks more complete. This also shows the container project as undeclared in aop-mc-int which is not true. It still doesn't give a way to verify or resolve dependencies consistently in one place across an assembly. Running the same thing in the microcontainer/build project showed no dependencies at all. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107877#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...