-
Notifications
You must be signed in to change notification settings - Fork 38
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
Use maven publish plugin for central publishing #256
Conversation
This simplifies setup using the gradle maven publish plugin for publishing to central. This removes jcenter publishing, but publishing just to central covers jcenter since it proxies it anyway. https://github.com/vanniktech/gradle-maven-publish-plugin This requires added local gradle properties (recommended to put them in your ~/.gradle/gradle.properties) for signing and auth, described here: https://github.com/vanniktech/gradle-maven-publish-plugin#where-to-upload-to Most significantly, this automatically handles publishing the gradle plugin marker artifact as well so that it can be used directly in `plugins {...}`
This is... an interesting error
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good, just one query about whether it's still possible to publish to Bintray. CI also appears to be broken, potentially it might be the case of setting this flag to disable signing on CI: vanniktech/gradle-maven-publish-plugin#114
Looks like it's working now 👍 . Would be worth exploring enabling snapshots btw, makes it easy for people to try new versions. This plugin handles it well too as long at the version ends in |
This simplifies setup using the gradle maven publish plugin for publishing to central. This removes jcenter publishing, but publishing just to central covers jcenter since it proxies it anyway.
https://github.com/vanniktech/gradle-maven-publish-plugin
This requires added local gradle properties (recommended to put them in your ~/.gradle/gradle.properties) for signing and auth, described here: https://github.com/vanniktech/gradle-maven-publish-plugin#where-to-upload-to
Most significantly, this automatically handles publishing the gradle plugin marker artifact as well so that it can be used directly in
plugins {...}
This also makes snapshots development (
./gradlew uploadArchives
when the version ends in-SNAPSHOT
) and local development./gradlew install
) easierResolves #267