anchor.diff:  ==== The FindBugs plugin has been removed
   
   The deprecated FindBugs plugin has been removed.
  -As an alternative, you can use the link:https://plugins.gradle.org/plugin/com.github.spotbugs[SpotBugs plugin] from the link:https://plugins.gradle.org[Gradle Plugin Portal].
  +As an alternative, you can use the link:https://plugins.gradle.org/plugin/com.github.spotbugs[SpotBugs plugin] from the link:https://plugins.gradle.org/search?term=spotbugs[Gradle Plugin Portal].
   
   ==== The JDepend plugin has been removed
   
  
positive.code: ==== Changing the pom packaging no longer changes the artifact extension
  
  Previously, the extension of the main artifact published to a Maven repository, typically a _jar_, was changed during publishing if the pom packaging was not _jar_, _ejb_, _bundle_ or _maven-plugin_.
  This behavior let to broken Gradle Module Metadata and was difficult to understand due to different handling of different packaging types.
  Build authors can change the artifact name when the artifact is created to obtain the same result as before - e.g. by setting `jar.archiveExtension.set(pomPackaging)`.
  
  ==== Ivy.xml published for Java libraries contains more information
  
negative.code: 
  ==== Gradle Module Metadata is always published
  
  https://blog.gradle.org/gradle-metadata-1.0[Gradle Module Metadata], officially introduced in Gradle 5.3, was created to solve many of the problems that have plagued dependency management for years, in particular, but not exclusively, in the Java ecosystem.
  With Gradle 6.0, Gradle Module Metadata is enabled by default.
  This means, if you are publishing libraries with Gradle, using the <<publishing_maven.adoc#,maven-publish>> or <<publishing_ivy.adoc#,ivy-publish>> plugin, the Gradle Module Metadata file is always published *in addition* to the traditional metadata.
  The traditional metadata file will contain a marker so that Gradle knows that there is additional metadata to consume.
  