Unpublished Gradle metadata is breaking builds

[dreis2211]

Hi,

our builds don't really work at the moment because the Gradle metadata file is not published, although the pom.xml marker suggests it.

https://repo1.maven.org/maven2/p6spy/p6spy/3.9.1/p6spy-3.9.1.pom

<!--  This module was also published with a richer model, Gradle metadata,   -->
<!--  which should be used instead. Do not delete the following line which   -->
<!--  is to indicate to Gradle or any Gradle module metadata file consumer   -->
<!--  that they should prefer consuming it instead.  -->
<!--  do_not_remove: published-with-gradle-metadata  -->

This currently breaks when doing ./gradlew build --refresh-dependencies and is a show-stopper for us at the moment because Artifactory is returning 403 on virtual repos when it doesn't find artifacts (https://www.jfrog.com/jira/browse/RTFACT-8765)

A quick fix would be to disable metadata generation

    tasks.withType(GenerateModuleMetadata) {
        enabled = false
    }

Or by including the respective .module file in the publication step.

Cheers,
Christoph

[typekpb]

@dreis2211 please have a look at the PR: #517 should be a fix for the reported issue

[typekpb]

@dreis2211 I see your point, let's give it a try with the next release. would ask you for the feedback afterwards.