Emond Papegaaij created SHRINKWRAP-488: ------------------------------------------ Summary: Dependency management with scopes are not resolved correctly Key: SHRINKWRAP-488 URL: https://issues.jboss.org/browse/SHRINKWRAP-488 Project: ShrinkWrap Issue Type: Bug Components: ext-resolver Affects Versions: 1.2.2 Reporter: Emond Papegaaij If the scope of an indirect dependency is changed in the dependencyManagement of your pom, this scope is not correctly taken into account when resolving compileAndRuntimeDependencies. I've created a very minimal testcase to demonstrate this problem: https://github.com/papegaaij/resolve-dep This testcase resolves the dependencies using: {code} File[] jars = Maven.configureResolver().workOffline() .loadPomFromFile("pom.xml") .importCompileAndRuntimeDependencies().resolve() .withTransitivity().as(File.class); {code} The pom only defines 1 compile dependency (shrinkwrap-impl-base), which depends on 2 others (shrinkwrap-api and shrinkwrap-spi). shrinkwrap-api has a dependencyManagement with scope provided, so I expect this resolution to yield 2 files (base and spi), but it yields all 3. -- This message was sent by Atlassian JIRA (v6.3.1#6329)