Maven classpathworkspace resolver shouldn't assume classes are under target/classes ----------------------------------------------------------------------------------- Key: SHRINKRES-149 URL: https://issues.jboss.org/browse/SHRINKRES-149 Project: ShrinkWrap Resolvers Issue Type: Feature Request Security Level: Public(Everyone can see) Affects Versions: 2.0.0 Reporter: Matthieu Baechler To avoid conflicting builds between Maven and Eclipse, I put eclipse build into a "eclipse-build/classes" directory. Considering this configuration, with the following code : {code:java} Maven.resolver() .offline() .loadPomFromFile("../../pom.xml") .resolve("com.linagora.obm:services-module:2.6.0-SNAPSHOT") .withClassPathResolution(true) .withTransitivity() .asFile(); {code} Maven resolver find my services-module on the classpath, but when trying a build a jar, it fails in MavenResolvedArtifactImpl.artifactToFile : {code:java} // SHRINKRES-102, allow test classes to be packaged as well File root = new File(artifact.getFile().getParentFile(), "target/classes"); {code} In my case, target/classes contains maven build result and not what's on the classpath. Can this resolver use the classes on the classpath instead ?