This has been one of two Maven features that have kept me from going fully to Gradle, so thanks so much for taking this challenge on.
The other is the inability to print console logs from unit tests when running TestNG. There is a JIRA for that one. Thanks again. From: Eric Berry <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Tue, 30 Aug 2011 23:44:57 -0500 To: Gradle Users <[email protected]<mailto:[email protected]>> Subject: [gradle-user] [RFC][RFH] A release plugin. I've been working on a release plugin that's similar to the Maven release plugin. The process it follows is: 1. Check to see if source is out of date 2. Check to see if source needs to be checked in. 3. Check for SNAPSHOT dependencies if required. 4. Build && run Unit tests (build task) 5. Run any other tasks the user specifies in convention. 6. Update Snapshot version if used (to non-snapshot version) 7. Commit un-Snapshot update (if done) 8. Create tag of release. 9. Update version to next version. 10. Commit version update. I have support for Bazaar and SVN, and I'm looking for help getting support for Git and Mercurial, as well as any advice. If anyone's interested the source can be downloaded on the launchpad project: https://launchpad.net/gradle-release If you have Bazaar installed it can be downloaded like so: bzr branch lp:gradle-release The plugin can be installed via the 'installPlugin' gradle task. Cheers, Eric -- Learn from the past. Live in the present. Plan for the future. Blog: http://eric-berry.blogspot.com<http://eric-berry.blogspot.com/> jEdit <http://www.jedit.org<http://www.jedit.org/>> - Programmer's Text Editor Bazaar <http://bazaar.canonical.com<http://bazaar.canonical.com/>> - Version Control for Humans
