v6.0.0
Manifest.mf entries are no longer inputs of Jar
tasks. It has the following implications. A change of an entry (e.g. project status, branch name etc.) will not cause Jar
tasks to rerun. It means in some cases you can have stale metadata. The benefit is much better cacheable Jar
tasks. Local task avoidance or Gradle distribute caching will only rebuild the archive when there is an actual content change. This is very important for shaded jars which are expensive to build.
Dependencies info plugin is now avoiding the resolution of deprecated configurations to follow the recommended usage of each configuration by Gradle.