You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't want to publish an java artifact and just want the plugin to bump the project version in my case. I know this might sound dumb using this plugin then, but it was the quickest solution to me. I'm currently thinking about developing an own plugin that is capable of bumping versions stored in different file formats which would be a cleaner solution but might conflict with other plugin executions.
However, as of now I'm bypassing the publication by registering a dummy task.
task publish(type: DefaultTask) {
group ='publish'
description ='Dummy publish to pass the verification phase of the gradle-semantic-release-plugin'
}
I wonder what you think about adding an option that would simply skip the publication. As of writing this, another option came to my mind: Maybe it would be nice to add an option that one can specify the task that should be executed for publication. Here is a quick example:
Maybe it would be nice to add an option that one can specify the task that should be executed for publication
It seems very nice. Currently we only have a 'smart' way which detects necessary publication tasks, but this feature will help users who need to handle corner cases.
Something of a not-very-corner case: I'm writing a spring boot application that's going to be deployed inside a docker image, and they have a handy bootBuildImage task that builds the image....
I don't want to publish an java artifact and just want the plugin to bump the project version in my case. I know this might sound dumb using this plugin then, but it was the quickest solution to me. I'm currently thinking about developing an own plugin that is capable of bumping versions stored in different file formats which would be a cleaner solution but might conflict with other plugin executions.
However, as of now I'm bypassing the publication by registering a dummy task.
I wonder what you think about adding an option that would simply skip the publication. As of writing this, another option came to my mind: Maybe it would be nice to add an option that one can specify the task that should be executed for publication. Here is a quick example:
The text was updated successfully, but these errors were encountered: