anchor.diff:  
   
   === Daemon build
  -In some cases, you need to run a Maven build in the background. The first case is when the build itself starts some application (eg. `mvn spring-boot:run`). The second case is when you are building a project that is too big so can do some other operation in the meantime let the Maven built run in the background.
  +In some cases, you need to run a Maven build in the background. The first case is when the build itself starts some application (eg. `mvn spring-boot:run`). The second case is when you are building a project that is too big so can do some other operation in the meantime let the Maven build run in the background.
   In these cases you can specify that the build should be used as a daemon, which means that ShrinkWrap Resolver runs the build in a new separated thread:
   [source,java]
   ....
  
positive.code:   .importBuildOutput().as(WebArchive.class);
  ----
  
  If you execute some custom tasks which modifies the built result you might want to perform Gradle Importer build in a custom directory. To do this you need
  to pass an argument `-PbuildDir=your-build-directory` and then use the `importBuildOutput("your-build-directory/libs/your-output-file")` method.
  
  Additional Gradle Importer full usage example can be found under https://github.com/mmatloka/arquillian-gradle-sample .
  
negative.code: 
  * additional methods & functions (eg. for ignoring build failures or making the build output quiet)
  
  * Java class representing a build project
  
  * easy getting a ShrinkWrap Archive created by the build
  
  