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

Replace novoda/bintray-release with bintray/gradle-bintray-plugin #461

Merged
merged 5 commits into from
Oct 18, 2018

Conversation

chibatching
Copy link
Contributor

Replace novoda/bintray-release with bintray official bintray/gradle-bintray-plugin to get rid of blocker of #448.

I can't test upload because I don't know the credentials, but you can check generated artifacts and pom.

Execute

./gradlew clean install

And please verify the files at $HOME/.m2/repository/com/github/maskarade/android/orma uploaded to bintray.

@@ -1,5 +1,4 @@
apply plugin: 'java'
apply plugin: 'com.novoda.bintray-release'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is apply plugin: 'com.github.dcendents.android-maven' not needed?
Others build.gradle has the line.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This module and processor module is not android project.
So, we don't need this plugin.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just understand, thanks!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

}
developers {
developer metadata.developer
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some metadata is not contained in the original POM file, but sometimes it is useful for example license tools.
If we don't need this, I'll remove these.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🆒

publish.gradle Outdated

bintray {
//TODO Set appropriate authorize information
user = "foo"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use ext.bintrayUser, which should be defined in ~/.gradle/gradle.properties.

publish.gradle Outdated
bintray {
//TODO Set appropriate authorize information
user = "foo"
key = "bar"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use ext.bintrayKey, which should be defined in ~/.gradle/gradle.properties, too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed at da5acf2 😄

@gfx
Copy link
Member

gfx commented Oct 18, 2018

Coooool!! ㊗️

I'll merge it soon after user and key are fixed.

@chibatching
Copy link
Contributor Author

I am worried about the uploadBintray task deploying appropriate bintray packages.

This PR is created based on My library has multi-module like orma but it is deployed the single bintray package and multi artifacts.

Android-Orma has the multi bintray package and single artifact per package.
So, I set name and desc per module (), but I can't confirm this works right. 😭

@chibatching
Copy link
Contributor Author

CI failed with Cannot get property 'bintrayKey' on extra properties extension as it does not exist 😢

@k-kagurazaka
Copy link
Member

Properties in ~/.gradle/gradle.properties cannot be accessed by ext.
Please use user = property('bintrayUser') format.

@k-kagurazaka
Copy link
Member

Sorry for my wrong knowledge 🙇
Build is still failed 😭

@k-kagurazaka
Copy link
Member

@gfx Does Circle CI have credentials?
In my understand, Circle CI do build but doesn't publish artifacts until now.

@chibatching
Copy link
Contributor Author

Some value needs on Gradle configuration phase, so I'll set dummy value if the property does not exist.

@chibatching
Copy link
Contributor Author

Pass!!

@chibatching
Copy link
Contributor Author

I misunderstand the behavior. Right behavior is below.

  1. Bintray closure is executed on the configuration phase.
  2. property(String name) method is executed, and throw MissingPropertyException if property doesn't exist.
  3. Crash!

So, I change method findProperty(String name), it returns null if property doesn't exist.

@gfx
Copy link
Member

gfx commented Oct 18, 2018

LGTM! Thanks for the effort!

@gfx gfx merged commit f5833a4 into maskarade:master Oct 18, 2018
@chibatching chibatching deleted the replace_bintray_plugin branch October 18, 2018 01:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants