Merge pull request #3399: Convert all maven-publish tests to produce and verify Gradle metadata With this change, all subtypes of `AbstractMavenPublishIntegrationTest` will enable production of Gradle metadata by setting the `-Dorg.gradle.internal.publishGradleMetadata` flag. Only java components are currently published to Gradle metadata, and in these cases the published `.module` file is validated.
There are a couple of exceptions to this:
- Gradle metadata does not yet support dependency excludes. For these cases, the `.module` file is successfully produced, but published dependencies do not have any exclusions. Tests for this functionality have been converted, but we do not attempt to resolve the published `.module` file or verify the published dependencies. - Where the original component artifacts are modified via the `MavenPublication`, Gradle cannot produce a valid metadata file, and attempting to publish will fail. Module metadata publishing has been disabled for tests that exercise this functionality.