"bdaw" wrote : So with cargo most off those dependencies are not present in my plugin classpath. If I don't use test scope for dependencies everything is fine. | Any idea? Before I start to debug maven.... ;) | | So the results of mavenProject.getTestClasspathElements() is different depending on whether you're using the cargo plugin or not? That seems strange. I guess you could look at the cargo source to see if/where it is modifying the test classpath. If there's nothing you can do to change cargo's behavior maybe you could add the dependencies you need for your plugin as plugin dependencies instead of project test dependencies. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105171#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...