[GRADLE-257] Release plugin Created: 08/Oct/08 Updated: 24/Jan/17 Resolved: 24/Jan/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | New Feature | ||
Reporter: | Phil Messenger | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 13 |
Description |
It would be nice to have a proper release plugin to perform the tasks usually associated with building and releasing a project. I've written a plugin for work that could form the basis of this, though it's clearly tailored for our particular purposes. I'll create a page on the wiki with some more information. This also depends on |
Comments |
Comment by Christian Gnüchtel [ 07/Mar/12 ] |
There is a release plugin: It is even referenced in the Gradle Wiki: Does anybody experience with this plugin? Is it similar to the Maven release plugin? |
Comment by Benjamin Muschko [ 15/Nov/16 ] |
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
Comment by Benjamin Muschko [ 24/Jan/17 ] |
There are plenty of release plugins out there by now. Requirements are usually fairly specific (e.g. workflow, SCM, versioning strategy). It doesn't really make sense to have one specific release plugin in Gradle core. |