anchor.diff:  This will publish your package to all configured publication repositories.
   There are also other tasks that allow you to publish to a single repository even when multiple ones are defined.
   +
  -Note that the Maven Publish Plugin does not publish *source and Javadoc JARs* by default, but this can easily be configured as explained <<publishing#sec:publishing_custom_artifacts_to_maven,elsewhere in the user manual>>.
  +Note that the Maven Publish Plugin does not publish *source and Javadoc JARs* _by default_, but this can easily be activated as explained in <<building_java_projects.adoc#sec:java_packaging,the guide for building java projects>>.
   
   [[migmvn:automatic_conversion]]
   == Performing an automatic conversion
  
positive.code:  * <<working_with_files#sec:creating_archives_example,Creating custom archive tasks>>
   * Using a suitable community plugin from the https://plugins.gradle.org/[Gradle Plugin Portal]
  
  If you're lucky and don't have many plugins or much in the way of customisation in your Maven build, you can simply run
  
  [listing.terminal]
  ----
  
negative.code: ====
  <1> Attaches version 1.2.12 of Log4J to the `implementation` configuration (scope)
  
  The string identifier takes the Maven values of `groupId`, `artifactId` and `version`, although Gradle refers to them as `group`, `module` and `version`.
  
  The above example raises an obvious question: what is that `implementation` configuration?
  It's one of the standard dependency configurations provided by the <<java_plugin#tab:configurations,Java Plugin>> and is often used as a substitute for Maven's default `compile` scope.
  