[
https://issues.apache.org/jira/browse/SCM-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964861#comment-17964861
]
Olivier Lamy commented on SCM-669:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#877|https://github.com/apache/maven-scm/issues/877].
> Accuwork Integration does not seem to work
> ------------------------------------------
>
> Key: SCM-669
> URL: https://issues.apache.org/jira/browse/SCM-669
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-accurev
> Environment: windows XP, Maven 2.2.1, maven scm provider accurev
> 1.6.1, maven release plugin 2.2
> Reporter: L. Compère
> Priority: Major
>
> In the process of a release using the maven release plugin, promotes are made
> by the plugin once the next development version has been written in the
> files. When such a promote is done, Accurev requires an issue number to be
> provided for the change package.
> When no issue number is provided, the command line execution of the maven
> release simply freezes and there seems to be no other choice but to kill the
> process.
> This seems to happen because some kind of popup is waiting for user
> interaction in the background... but we, at the mvn release command line,
> don't ever see this popup, so it just feels like the command is frozen
> somewhere.
> Anybody had this problem? Any solutions/workarounds?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
