anchor.diff:  +
   This doesn't mean that you need to verify every artifact at every stage, although doing so can help you quickly identify the source of a problem.
   You can just focus on the critical output such as final reports and the artifacts that are published or deployed.
  ++
  +You will need to factor in some inherent differences in the build output that Gradle produces compared to Maven.
  +Generated POMs will contain only the information needed for consumption and they will use `<compile>` and `<runtime>` scopes correctly for that scenario.
  +You might also see differences in the order of files in archives and of files on classpaths.
  +Most differences will be benign, but it's worth identifying them and verifying that they are OK.
    3. <<migmvn:automatic_conversion,Run an automatic conversion>>
   +
   This will create all the Gradle build files you need, even for <<migmvn:multimodule_builds,multi-module builds>>.
  
positive.code: === Declaring repositories
  
  Gradle allows you to retrieve declared dependencies from any Maven-compatible or Ivy-compatible repository.
  Unlike Maven, it has no default repository, so you have to declare at least one.
  In order to have the same behavior as your Maven build, just configure <<repository_types#sub:maven_central,Maven Central>> in your Gradle build, like this:
  
  .Configuring the build to use Maven Central
  
negative.code: 
  == Further reading
  
  This chapter has covered the major topics that are specific to migrating Maven builds to Gradle. All that remain are a few other areas that may be useful during or after a migration:
  
   * Learn how to configure Gradle's <<build_environment#build_environment,build environment>>, including the JVM settings used to run it
   * Learn how to <<organizing_gradle_projects#organizing_gradle_projects,structure your builds effectively>>
  