Skip to content

Detekt Deployment is missing Gradle Module files #2878

Description

@cortinico

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).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions