Hook to publish release about gradle-release-plugin

[netzwerg]

Calling the release task will not build a snapshot, but build a release, hence your build release scenario is covered.

Concerning publish release: This is out of this plugin's scope. The recommended approach depends on your definition of "publish":

• For Artifactory publishing, I recommend the Gradle Artifactory Plugin
• For GitHub publishing, you might want to look into my gradle-release-pub-plugin. It is two years old and very abandoned (there was no real interest), but it might serve as an inspiration.
• ...

Hope this helps – Cheers, Rahel

[chrisharris77]

Thank you Rahel. I completely agree it's not a release plugin's job to perform a publish. I am using maven-publish plugin. But the problem I have is that there is no way to invoke the publish plugin at the right time in the middle of the release i.e. when version.txt contains the release version number. I can only publish before or after the whole release task runs - which results in publishing a snapshot not a release. Regards, Chris

…

On Dec 14, 2016, at 3:54 AM, Rahel Lüthy ***@***.***> wrote: Calling the release task will not build a snapshot, but build a release, hence your build release scenario is covered. Concerning publish release: This is out of this plugin's scope. The recommended approach depends on your definition of "publish": For Artifactory publishing, I recommend the Gradle Artifactory Plugin For GitHub publishing, you might want to look into my gradle-release-pub-plugin. It is two years old and very abandoned (there was no real interest), but it might serve as an inspiration. ... Hope this helps – Cheers, Rahel — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[netzwerg]

Yep, your are right, there are currently no hooks to perform work in between the "tag version" and "update version" steps.

However, you could perform a git checkout <tag> right after the completion of release, and then call build and publish afterwards – could that work for you?

[chrisharris77]

I suppose that would be a workaround if I can get the tag.

It would be much nicer to not have to drop to executing git commands though. It seems like doing work when the version is set to the release version would be a very common scenario. What about making the release task be a wrapper for sub tasks? Then users could choose to the release task as is, or invoke subtasks and mix with other tasks e.g. publish?

[netzwerg]

The tag is exposed via project.release.tagName.

I completely agree that we should offer cleaner solution – I am very open to pull requests. The suggested approach is really only a workaround, just so you are not blocked until a better solution is available.

[chrisharris77]

OK I'll try that thanks.