[
http://jira.codehaus.org/browse/SCM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170598#action_170598
]
Olivier Lamy commented on SCM-450:
----------------------------------
So if you want to prevent deployement you have to bind this mojo between
install and deploy.but as we don't have any phase between install and deploy.
The phase to bind it is install.
But it will break multi modules build if you want only install all of them.
Only the first project will be installed.
So why not...
> Add option to check for up to date local checkout
> -------------------------------------------------
>
> Key: SCM-450
> URL: http://jira.codehaus.org/browse/SCM-450
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-plugin
> Reporter: Paul Gier
> Assignee: Olivier Lamy
> Fix For: 1.2
>
>
> It would be helpful if the deploy plugin had the ability to check the local
> workspace against the scm (svn, cvs, etc.) to make sure that everything is up
> to date and there are not local changes before deploying the artifact. This
> would mainly be useful when deploying snapshots since the release plugin
> already handles this for release versions.
> This would be useful to prevent someone (or at least warn them) from
> deploying a snapshot that cannot be reproduced.
--
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
