maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MRELEASE-504) Check if working copy is up-to-date
Date Sat, 18 Sep 2010 03:50:34 GMT

     [ http://jira.codehaus.org/browse/MRELEASE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter closed MRELEASE-504.
---------------------------------

    Resolution: Duplicate
      Assignee: Brett Porter

> Check if working copy is up-to-date
> -----------------------------------
>
>                 Key: MRELEASE-504
>                 URL: http://jira.codehaus.org/browse/MRELEASE-504
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: prepare
>    Affects Versions: 2.0-beta-9
>            Reporter: Stefan Seelmann
>            Assignee: Brett Porter
>
> It would be nice if the release:prepare goal could check if the working copy is up-to-date.
> For svn the local and the remote revision number could be compared.
> For git the it should also be possible to compare commit IDs.
> My current problem that release:prepare fails if there is a newer revision in the SVN
repository:
> -----------------------------------------------------------
> [INFO] Unable to commit files
> Provider message:
> The svn command failed.
> Command output:
> svn: Commit failed (details follow):
> svn: File '/firstmodule/trunk/pom.xml' is out of date
> -----------------------------------------------------------

-- 
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

        

Mime
View raw message