anchor.diff:  
   |====
   
  -11. Control sources of resolution. ShrinkWrap Resolvers allows you to specify where do you want to resolve artifacts from. By default, it uses classpath (also known as Maven Reactor) and Maven Central repository, however you can programmatically alter the behavior.
  +Control sources of resolution::
  +ShrinkWrap Resolvers allows you to specify where do you want to resolve artifacts from. By default, it uses classpath (also known as Maven Reactor) and Maven Central repository, however you can programmatically alter the behavior.
   +
   [source,java]
   ----
  
positive.code: Runtime in convenience methods means all the Maven scopes that are used in application runtime, which are +compile+, +runtime+, +import+ and +system+. If you need to select according to Maven scopes, go for +importDependencies(ScopeType...)+ instead.
  ====
  
  3. Specifying profiles to be activated. By default, ShrinkWrap Resolvers activates profiles based on property value, file presence, active by default profiles, operating system and JDK. However, you can force profiles in same way as you would do via +-P+ in Maven.
  +
  [source,java]
  ----
  
negative.code: File file = artifact.asFile();
  ----
  
  Resolution of artifacts as collection::
  It might be convenient to work with +List+ interface instead of an array. For such cases, you can wrap the results of resolution using following call:
  +
  [source,java]
  ----
  List<File> files = Maven.resolver().resolve("G:A:V")
      .withTransitivity().asList(File.class);
  List<JavaArchive> files = Maven.resolver().resolve("G:A:V")
      .withTransitivity().asList(JavaArchive.class);
  ----
  +
  
  Transitive dependency exclusion::
  In case you need to resolve an artifact while avoiding some of its dependencies, you can follow concept of +<exclusions>+ known for Maven. Following snippet shows how to exclude +G:B+ while resolving +G:A:V+.
  +
  [source,java]
  ----
  