[
https://issues.apache.org/jira/browse/SCM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961592#comment-17961592
]
ASF GitHub Bot commented on SCM-450:
------------------------------------
jira-importer opened a new issue, #665:
URL: https://github.com/apache/maven-scm/issues/665
**[Paul
Gier](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pgier)**
opened
**[SCM-450](https://issues.apache.org/jira/browse/SCM-450?redirect=false)** and
commented
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.
---
No further details from
[SCM-450](https://issues.apache.org/jira/browse/SCM-450?redirect=false)
> Add a mojo to check for up to date local checkout
> -------------------------------------------------
>
> Key: SCM-450
> URL: https://issues.apache.org/jira/browse/SCM-450
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-plugin
> Reporter: Paul Gier
> Assignee: Olivier Lamy
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
