anchor.diff:  
   == Our advice
   
  -_TL;DR_ If you are not forced to use Maven, don't use it.
  +_TL;DR_ We recommend using Gradle.
   
   Everything QiWeb is automated using Gradle, from the SDK build to the baking and publication of a website embedding
   versioned documentation for past, current and development releases.
  
positive.code: 
  If you prefer another build tool or even want to write shell scripts on your own, its still possible to use QiWeb.
  
  A QiWeb application is a plain old java program (main class) so it's a no brainer to run it production mode.
  
  Tests of QiWeb applications are simple JUnit tests, again, no brainer to run.
  
  Obvisouly, the classpath should be set up properly with regard to your application dependencies.
  
  Finally, to make QiWeb development mode work in another build tool you'll probably need to write some code.
  Have a look at the Gradle and Maven support source code for insights in this matter.
  
  If you get to something reusable, please contribute it.
  We are very interested in such a contribution.
  
negative.code: 
  We love Gradle.
  Mainly for its DSL expressiveness and extensibility.
  But, Maven is very commonly used and changing the build tool used in an organisation can be challenging.
  We implement new features in Gradle support and port them to Maven support afterwards, if even possible.
  In other words, work on the QiWeb Maven support is motivated by ease of adoption only.
  
  So, do we need to say more?
  