Skip to content
This repository has been archived by the owner on Jan 18, 2021. It is now read-only.

Bintray settings are not applied from shipkit.gradle #791

Open
mockitoguy opened this issue Mar 5, 2019 · 2 comments
Open

Bintray settings are not applied from shipkit.gradle #791

mockitoguy opened this issue Mar 5, 2019 · 2 comments

Comments

@mockitoguy
Copy link
Member

Standard way of configuring Bintray does not work in some projects. It seems like a bug in Gradle.

Typical content in "gradle/shipkit.gradle":

allprojects { 
   plugins.withId("com.shipkit.bintray") {
       bintray {
          ...
       }
   }
}

Problem is that bintray settings are not applied in some projects. For example, I needed this workaround: linkedin/dynamometer#86

Given that we withId("...") cannot be trusted, perhaps we update the configuration along with the workaround above. Thoughts?

@epeee
Copy link
Contributor

epeee commented Mar 5, 2019

Hmm, that's interesting.
I will try do dig into this one in the next days.

@mstachniuk
Copy link
Contributor

I might be connected with Removal of deferred configuration behavior: https://docs.gradle.org/current/userguide/publishing_maven.html#publishing_maven:deferred_configuration

Prior to Gradle 5.0, the publishing {} block was (by default) implicitly treated as if all the logic inside it was executed after the project is evaluated. This behavior caused quite a bit of confusion and was deprecated in Gradle 4.8, because it was the only block that behaved that way.

I see the changes between Gradle 4.5 & 4.10.2 in last days: linkedin/dynamometer@8f7efac#diff-fd9d61e37d939c941e7a62077f38d62d

But I don't know how it's connected with Bintray plugin.

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

No branches or pull requests

3 participants