maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Gardner (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (SCM-611) AccuRev - call replica sync before export
Date Sun, 27 Feb 2011 04:46:22 GMT
AccuRev - call replica sync before export
-----------------------------------------

                 Key: SCM-611
                 URL: http://jira.codehaus.org/browse/SCM-611
             Project: Maven SCM
          Issue Type: Improvement
          Components: maven-scm-provider-accurev
    Affects Versions: 1.5
            Reporter: Grant Gardner
            Priority: Minor


When using the AccuRev 4.9 feature that allows export of a specific version (transaction id),
this will fail if you are using a replica server where this transaction is not available.

This appears for me in the[Bamboo maven scm integration|https://studio.plugins.atlassian.com/wiki/display/BMSCM/Home]
since Bamboo does its change detection against the AccuRev master server and passes the top
transaction id to an agent which exports the code from an AccuRev replica.

Unfortunately there isn't a nice way to detect if you are using a replica, apart from seeing
a warning message when you try to sync so fix is to just always call replica sync and ignore
any errors.

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