Hi,

I am trying to resolve the classpath of a Maven module, which also contains dependencies that appear in the parent pom as "managedDependencies". In my code (gist:62b2e4d7af4166ab7e94 · GitHub), ShrikWrap fails trying to resolve the dependencies to other modules from an specific module (the project has not been compiled). However, it works fine for single-module projects. My dependencies are:

<dependency>

  <groupId>org.jboss.shrinkwrap.resolver</groupId>

  <artifactId>shrinkwrap-resolver-api</artifactId>

  <version>2.2.0-beta-2</version>

  </dependency>

  <dependency>

  <groupId>org.jboss.shrinkwrap.resolver</groupId>

  <artifactId>shrinkwrap-resolver-api-maven</artifactId>

  <version>2.2.0-beta-2</version>

  </dependency>

  <dependency>

  <groupId>org.jboss.shrinkwrap.resolver</groupId>

  <artifactId>shrinkwrap-resolver-spi</artifactId>

  <version>2.2.0-beta-2</version>

  </dependency>

  <dependency>

  <groupId>org.jboss.shrinkwrap.resolver</groupId>

  <artifactId>shrinkwrap-resolver-impl-maven</artifactId>

  <version>2.2.0-beta-2</version>

  </dependency>

  <dependency>

  <groupId>org.jboss.shrinkwrap.resolver</groupId>

  <artifactId>shrinkwrap-resolver-impl-maven-archive</artifactId>

  <version>2.2.0-beta-2</version>

  </dependency>

Any idea? Do I need to solve the dependency graph between modules and compile all of them before resolving the module classpath?