When you want to release, this failing IT should be excluded in the pom (using the pomExcludes in the m-invoker-p) with a comment.
If somebody in the near future tries to build the project based on this tagged version, it must be possible according to the Maven convention, no extra manually added values. I'll be gone for a while, so I won't block this. I expect Stephen can fix this and than it's good to go. - Robert Date: Tue, 18 May 2010 22:41:57 +0100 From: [email protected] To: [email protected] Subject: [mojo-dev] [VOTE] Release versions-maven-plugin version 1.2 Folks, It has been a little while since the last release of versions-maven-plugin, a number of important issues have been resolved and I would like to roll a release. We solved 8 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11830&styleName=Html&version=15914 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=11830&resolution=-1&sorter/field=updated&sorter/order=DESC The new site has just been deployed here: http://mojo.codehaus.org/versions-maven-plugin Snapshot have been published on http://snapshots.repository.codehaus.org/org/codehaus/mojo/versions-maven-plugin The one failing integration test is because the integration tests use a local repo as a remote repo and hence are missing correct metadata for range resolution This vote will be open for 72 hours and will use lazy consensus. [+1] release it [0] don't care [-1] don't release! Thanks, Stephen P.S. Here is my +1 _________________________________________________________________ New Windows 7: Find the right PC for you. Learn more. http://windows.microsoft.com/shop
