Ability to promote staging repository about gradle-nexus-plugin HOT 10 CLOSED

These days I am not directly publishing to Maven Central anymore. I always go through Bintray which provides a convenient way to sync with Maven Central. Therefore, I have little incentive to spend time on this functionality.

If you are interested in having this functionality, you'll need to provide a pull request. The Nexus REST API sounds like the right approach. In case you go are planning to implement this functionality, please try to avoid additional dependencies on HTTP libraries especially Groovy's HTTPBuilder.

from gradle-nexus-plugin.

What do you propose to use instead of HTTPBuilder? Running curl process from OS?

from gradle-nexus-plugin.

HttpClient or better HttpURLConnection. Thinking about it, I don't actually want the functionality in this plugin. It should be a separate, complimentary plugin.

from gradle-nexus-plugin.

I am going to close this issue. It should be easy to write a plugin that applies and augments the functionality of the Nexus plugin with tasks using the Nexus API. Either way I don't see the functionality in this plugin. Also, I'd expect quite a bit of maintenance & required testing code coming out of this functionality which I won't have the time for. Should you ever create such a plugin, let me know and I am going to link to it from this plugin's documentation page.

from gradle-nexus-plugin.

I decided to write that plugin and in the end it turned out that there are some corner cases to support (so probably good for you that you haven't decide to have that feature :) ).
My plugin is upload mechanism agnostic (it just uses REST API), but I was thinking about better integration with gradle-nexus-plugin (when available). I wanted to reuse credentials provided for your plugin, but looking at your code it seems I could only try to find nexusPassword/nexusUsername or try to find upload task(s) and get credentials from they (if available). Do you have any other idea what could be done on that field?

from gradle-nexus-plugin.

I am not quite sure what other credentials you are looking for other than username/password. If you can give me more information, I might be able to give you a better answer.

from gradle-nexus-plugin.

After post my comment I realized that your plugin does not keep credentials itself, but only set authentication in a repository.

I was able to implement getting credentials with manually configured authentication section, but to use credentials set by your plugin I would need in addition to call my code in taskGraph.whenReady {} closure. That needs #47 and in addition one question to you: do taskGraph.whenReady {} closures are executed in the order they were created or it is not guaranteed?

from gradle-nexus-plugin.

Order is not guarenteed by Gradle.

from gradle-nexus-plugin.

Order is not guarenteed by Gradle.

So to be sure to be after your taskGraph.whenReady do I have to it in doFirst in my task or there is a better way?

from gradle-nexus-plugin.

I think I'd have to see the code but doFirst is a valid option. The only downside is going to be that you can't use the fields as input properties for your tasks.

from gradle-nexus-plugin.