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:  * The appropriate plugins to build the project (limited to one or more of the <<maven_plugin#maven_plugin,Maven>>, <<java_plugin#java_plugin,Java>> and <<war_plugin#war_plugin,War>> Plugins)
   
  See the <<build_init_plugin#sec:pom_maven_conversion_,Build Init Plugin chapter>> for a complete list of the automatic conversion features.
  
  One thing to bear in mind is that assemblies are not automatically converted.
  They aren't necessarily problematic to convert, but you will need to do some manual work.
  
negative.code: Even Ant properties and filesets are supported natively.
  To learn more, see <<ant#ant,Using Ant from Gradle>>.
  
  [TIP]
  ====
  It may be simpler and cleaner to just <<custom_tasks#custom_tasks,create custom task types>> to replace the work that Ant is doing for you. You can then more readily benefit from <<more_about_tasks#sec:up_to_date_checks,incremental build>> and other useful Gradle features.
  ====
  
  
  [[migmvn:unnecessary_plugins]]
  == Understanding which plugins you don't need
  