Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detekt Deployment is missing Gradle Module files #2878

Closed
cortinico opened this issue Jul 16, 2020 · 1 comment · Fixed by #2885
Closed

Detekt Deployment is missing Gradle Module files #2878

cortinico opened this issue Jul 16, 2020 · 1 comment · Fixed by #2885

Comments

@cortinico
Copy link
Member

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

@arturbosch
Copy link
Member

I would love to use only maven-publish!
The bintray plugin has some annoying bugs and looks unmaintained.

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

Successfully merging a pull request may close this issue.

2 participants