Expected Behavior
One of:
- Detekt
.module files are available on Bintray/MavenCentral.
- Detekt's
pom file shouldn't contain the Gradle Module marker: <!-- do_not_remove: published-with-gradle-metadata -->
Observed Behavior
Currently we have published pom files that contains the <!-- do_not_remove: published-with-gradle-metadata --> marker for all the modules (see here).
Steps to Reproduce
Module files are missing for all the modules (you can check it here).
The effective impact of this is probably what was reported in this comment #2814 (comment)
Context
I did some investigation and seems like the issue is that the gradle-bintray-plugin is failing to publish .module files: bintray/gradle-bintray-plugin#229
Given that we are applying both gradle-bintray-plugin and maven-publish (for publishing on artifactory), my suggestion is that we drop the gradle-bintray-plugin as we use only maven-publish for publishing (to hit bintray/artifactory).
Expected Behavior
One of:
.modulefiles are available on Bintray/MavenCentral.pomfile shouldn't contain the Gradle Module marker:<!-- do_not_remove: published-with-gradle-metadata -->Observed Behavior
Currently we have published
pomfiles that contains the<!-- do_not_remove: published-with-gradle-metadata -->marker for all the modules (see here).Steps to Reproduce
Module files are missing for all the modules (you can check it here).
The effective impact of this is probably what was reported in this comment #2814 (comment)
Context
I did some investigation and seems like the issue is that the gradle-bintray-plugin is failing to publish
.modulefiles: bintray/gradle-bintray-plugin#229Given that we are applying both
gradle-bintray-pluginandmaven-publish(for publishing on artifactory), my suggestion is that we drop thegradle-bintray-pluginas we use onlymaven-publishfor publishing (to hit bintray/artifactory).