Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Auto Closed
-
None
-
None
-
None
-
windows XP, Maven 2.2.1, maven scm provider accurev 1.6.1, maven release plugin 2.2
Description
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?