[
https://issues.apache.org/jira/browse/SCM-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962240#comment-17962240
]
ASF GitHub Bot commented on SCM-611:
------------------------------------
jira-importer opened a new issue, #821:
URL: https://github.com/apache/maven-scm/issues/821
**[Grant
Gardner](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=lwoggardner)**
opened
**[SCM-611](https://issues.apache.org/jira/browse/SCM-611?redirect=false)** and
commented
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.
---
**Affects:** 1.5
**Attachments:**
-
[SCM-611.patch](https://issues.apache.org/jira/secure/attachment/12718867/SCM-611.patch)
(_4.41 kB_)
> AccuRev - call replica sync before export
> -----------------------------------------
>
> Key: SCM-611
> URL: https://issues.apache.org/jira/browse/SCM-611
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-accurev
> Affects Versions: 1.5
> Reporter: Grant Gardner
> Assignee: Olivier Lamy
> Priority: Minor
> Fix For: 1.5
>
> Attachments: SCM-611.patch
>
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
