ShrinkWrap should be able to exclude its own and Arquillian's -impl archives ---------------------------------------------------------------------------- Key: SHRINKRES-30 URL: https://issues.jboss.org/browse/SHRINKRES-30 Project: ShrinkWrap Resolvers Issue Type: Feature Request Environment: Linux wallace 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21 22:07:10 UTC 2011 i686 i686 i386 GNU/Linux java version "1.7.0" Java(TM) SE Runtime Environment (build 1.7.0-b147) Java HotSpot(TM) Server VM (build 21.0-b17, mixed mode) JBoss AS 7.1.1.Final Arquillian 1.0.0.Final Reporter: Craig Ringer Labels: arquillian, dependency, maven, resolver, shrinkwrap I'm using ShrinkWrap via Arquillian 1.0.0.Final. When the Maven Dependency Resolver extension is used to load dependencies from a project pom, the ShrinkWrap and Arquillian dependencies are automatically included in produced ShrinkWrap archives. There doesn't appear to be any easy way to tell ShrinkWrap to leave its own -impl archives out, so a trivial test archive bloats to 31MB or more of Arquilian and ShrinkWrap archives and dependencies. Some of the transitive dependencies could cause conflicts with app server libraries, too. What I'd like to see is a very quick and easy way to tell the Maven resolver to exclude anything from ShrinkWrap or Arquillian when loading dependencies from a pom.xml, eg: {code} MavenDependencyResolver resolver = DependencyResolvers.use(MavenDependencyResolver.class) .includeDependenciesFromPom("pom.xml"); .excludeShrinkWrap().excludeArquillian(); // Imaginary for now {code} Currently one should be able to do something like: {code} MavenDependencyResolver resolver = DependencyResolvers.use(MavenDependencyResolver.class) .includeDependenciesFromPom("pom.xml") .exclusions("org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-impl-javaee", "org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven", "org.jboss.arquillian.junit:arquillian-junit-container", "org.jboss.as:jboss-as-arquillian-container-remote"); {code} ... but in my quick tests these exclusions appeared to have no effect.