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

Publishing workflow based on gradle's maven-publish #17

Closed
solonovamax opened this issue Aug 23, 2024 · 2 comments
Closed

Publishing workflow based on gradle's maven-publish #17

solonovamax opened this issue Aug 23, 2024 · 2 comments

Comments

@solonovamax
Copy link

Hi,

I'd like to propose a publishing workflow that's a bit more based on gradle's own built-in maven-publish.

I've implemented such a thing here myself: https://github.com/solo-studios/nyx/tree/master/src/main/kotlin/ca/solostudios/nyx/sonatype
note specifically:

  • SonatypePublishPlugin.kt
  • PublishToSonatypeMavenRepository.kt
  • SonatypeMavenRemotePublisher.kt

these classed are primarily copied directly from gradle's own interal code. do be warned, they do also use internal gradle apis.

some advantages of this approach are:

  • you interract with it in the exact same way as the normal maven-publish plugin.
  • the task structure is exactly the same
  • fully compatible with any existing plugins that use the existing maven-publish plugin

just thought I'd put this here as smth to consider.

@martinbonnin
Copy link
Member

Thanks for opening this.

At this time though there are no plans to add features or change the API. Feel free to fork the plugin if needed or users can use the code above as a reference but I'm marking this closed as there's nothing really actionable to be done here.

@solonovamax
Copy link
Author

Thanks for opening this.

At this time though there are no plans to add features or change the API. Feel free to fork the plugin if needed or users can use the code above as a reference but I'm marking this closed as there's nothing really actionable to be done here.

yeah no worries, just wanted to suggest it as it may have been desireable.

but, I already publish that plugin myself so I won't fork this plugin to add it.

@solonovamax solonovamax closed this as not planned Won't fix, can't repro, duplicate, stale Aug 27, 2024
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

No branches or pull requests

2 participants