You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2008/04/18 16:12:55 UTC
[jira] Created: (MDEPLOY-76) Add option to check for up to date
local checkout
Add option to check for up to date local checkout
-------------------------------------------------
Key: MDEPLOY-76
URL: http://jira.codehaus.org/browse/MDEPLOY-76
Project: Maven 2.x Deploy Plugin
Issue Type: New Feature
Reporter: Paul Gier
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
[jira] Moved: (SCM-450) Add option to check for up to date local
checkout
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier moved MDEPLOY-76 to SCM-450:
--------------------------------------
Complexity: Intermediate
Key: SCM-450 (was: MDEPLOY-76)
Project: Maven SCM (was: Maven 2.x Deploy Plugin)
> 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
>
> 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
[jira] Commented: (SCM-450) Add option to check for up to date
local checkout
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (SCM-450) Add a mojo to check for up to date local
checkout
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed SCM-450.
----------------------------
Resolution: Fixed
fixed rev 757289..
snapshot deployed.
To test it :
{code:xml}
<plugin>
<artifactId>maven-scm-plugin</artifactId>
<version>1.2-SNAPSHOT</version>
<executions>
<execution>
<id>check-local-modification</id>
<goals>
<goal>check-local-modification</goal>
</goals>
<phase>install</phase>
</execution>
</executions>
</plugin>
{code}
> Add a mojo 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
[jira] Updated: (SCM-450) Add a mojo to check for up to date local
checkout
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated SCM-450:
-----------------------------
Summary: Add a mojo to check for up to date local checkout (was: Add option to check for up to date local checkout)
> Add a mojo 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
[jira] Commented: (SCM-450) Add option to check for up to date
local checkout
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170484#action_170484 ]
Paul Gier commented on SCM-450:
-------------------------------
Ok, I agree. I have moved the issue to the maven scm plugin.
> 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
>
> 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
[jira] Updated: (SCM-450) Add option to check for up to date local
checkout
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated SCM-450:
-----------------------------
Assignee: Olivier Lamy
Fix Version/s: 1.2
A nice feature which could prevent some issues I have seen in my company.
IMHO :
* adding a configurable message
* adding a skip field (false by default) and display a warning when user enable this skip field
> 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
[jira] Updated: (SCM-450) Add option to check for up to date local
checkout
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier updated SCM-450:
--------------------------
Component/s: maven-plugin
> 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
>
> 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
[jira] Commented: (MDEPLOY-76) Add option to check for up to date
local checkout
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170457#action_170457 ]
Benjamin Bentmann commented on MDEPLOY-76:
------------------------------------------
IMHO, the Deploy Plugin should not be concerned with SCM stuff, these are two different domains. I believe it would be more sensible to extend the Maven SCM Plugin with such a check such that users can bind the SCM Plugin into the build.
> Add option to check for up to date local checkout
> -------------------------------------------------
>
> Key: MDEPLOY-76
> URL: http://jira.codehaus.org/browse/MDEPLOY-76
> Project: Maven 2.x Deploy Plugin
> Issue Type: New Feature
> Reporter: Paul Gier
>
> 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