[jira] Commented: (MRELEASE-284) prepare step should check if local sources are complete
[ http://jira.codehaus.org/browse/MRELEASE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127058 ] Dominique Jean-Prost commented on MRELEASE-284: --- Thanks to Samuel for explaining the case I thought to when I raised the bug. It's true that tools like scm are not there to fix communication problems within development teams, and the release plugin isn't there for neither. Anyway, I guess such a little enhancement (as I'm writing this, I wonder if I should not have raised this problem as an enhancement instead of a bug...) can improve the release process, which is never trivial to my mind. > prepare step should check if local sources are complete > --- > > Key: MRELEASE-284 > URL: http://jira.codehaus.org/browse/MRELEASE-284 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Dominique Jean-Prost > > Prepare step checks that all files are committed which is great. > Prepare step should also check that the local dir is complete, ie, that there > are no files missing in local dir (update needed) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-284) prepare step should check if local sources are complete
[ http://jira.codehaus.org/browse/MRELEASE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127055 ] Samuel Le Berrigaud commented on MRELEASE-284: -- I second that, one example of what can happen: - developer A work on trunk and gets ready to release, - developer B commits some code against trunk, - developer A does NOT do "svn up", - developer A runs "mvn release:prepare release:perform" Then the tag is created without the changed of developer B as is seems that (for svn at least) the plugins tags from "." the revision in the current directory. Maybe a better way would be to actually copy the trunk using the full URL instead of "."? Or better as Dominique suggest update the source code. > prepare step should check if local sources are complete > --- > > Key: MRELEASE-284 > URL: http://jira.codehaus.org/browse/MRELEASE-284 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Dominique Jean-Prost > > Prepare step checks that all files are committed which is great. > Prepare step should also check that the local dir is complete, ie, that there > are no files missing in local dir (update needed) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
