-
Notifications
You must be signed in to change notification settings - Fork 59
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
Publish gradle plugin properly #205
base: develop
Are you sure you want to change the base?
Conversation
b8943ca
to
991bece
Compare
991bece
to
f76b76a
Compare
Wonder what got this stuck |
Why don't we merge this? |
Hi! Thank you and sorry for the delay 🙏🏻 I tested publishing the plugin to the local Space repo and got some problems. I'm working on updating the script. |
Could we change the id to |
It's been 5 months, any updates? |
It's been a year, any updates? |
Hi there! I apologize for such the delay in publishing the plugin. It wasn't an immediate priority before. Now, I'm focusing on stabilizing the library, and simplifying the plugin application is currently in progress. The plugin will be published to GPP, and no buildscript configurations will ne necessary in the next few releases. |
following the guide at https://docs.gradle.org/current/userguide/publishing_gradle_plugins.html
this should make publishing to the gradle plugin repo easier
integrate this step into your publishing workflow or CI
tested with
publishToMavenLocal
allows to use atomicfu plugin with the following syntax:
fixes #56