"scott.stark(a)jboss.org" wrote : | All of these unused dependencies are in fact used, so what is this telling me? | The reason these ones are showing up is because of the renamed stuff. When the groupId changes from one version to another, then maven doesn't know that they are the same thing anymore. So the code might be compiling against a version picked up transitively. The way around this is to exclude the transitive dependency. Unfortunately there is currently no way to globally exclude a certain transitive dep. So you have to exclude it from each direct dependency where it is picked up. The junit dependency could probably be changed to a test scope instead of compile scope since it's not used by the main classes. I think that's why it's complaining about that one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132209#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...