"pgier" wrote : | I haven't heard anything about an option to exclude all transitive dependencies though. Is this something that you would really want? Then you would always have to update your transitive deps when any of the direct deps changed versions. It seems like this would have similar maintenance issues, just at a different time. | It's most important when transitive depenencies disagree with what the local project defines. But I personally don't like the way we end with unknown dependencies. It's not an issue for the current project directly, but more for those further down the line who have conflicts. I've even seen this in the MC project where the projects share a common definition of dependencies and are developed together. For one project it looks consistent, in another because of the addition of an extra dependency, it is not. mvn dependency:analyze doesn't show everything, so you don't know whether it is analyzing them correctly, the eclipse plugin gives a better indication of what the totality of dependencies are. Maybe being able to a dependency:analyze at the assembly level (which you can't do now) so you create a consistent view across the subproject dependencies in one place would be an alternate solution to the problem? Certainly being able to define the excludes once in microcontainer/build/pom.xml would be less verbose :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107798#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...