[
https://issues.apache.org/jira/browse/SCM-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962488#comment-17962488
]
ASF GitHub Bot commented on SCM-669:
------------------------------------
jira-importer opened a new issue, #877:
URL: https://github.com/apache/maven-scm/issues/877
**[L.
Compère](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=lcompere)**
opened
**[SCM-669](https://issues.apache.org/jira/browse/SCM-669?redirect=false)** and
commented
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?
---
No further details from
[SCM-669](https://issues.apache.org/jira/browse/SCM-669?redirect=false)
> 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)
