[SCM-279] Clearcase scm:update Hangs After Stream Configuration Has Changed (patch included)

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0-beta-4
• Fix Version/s: 1.0-rc1
• Component/s: maven-scm-provider-clearcase

Environment

Windows XP, Maven 2.0.4, JDK 1.4.2_10

ClearCase version 2003.06.00 (Fri Apr 18 13:06:18 2003)
@(#) MVFS version 2003.06.00 (Mar 24 2003 16:39:07)
cleartool 2003.06.00 (Wed Apr 2 21:00:48 2003)
db_server 2003.06.00 (Fri Mar 28 09:00:29 2003)
VOB database schema version: 54

• Assignee: Emmanuel Venisse
• Reporter: Dave Blumenfeld
• Created: 06/Feb/07 20:41
• Updated: 12/Mar/07 05:43
• Resolved: 12/Mar/07 05:43

Description

Maven hangs when running scm:update goal on a Clearcase snapshot view for a stream that has been rebased (see attached debug output). The same goal works fine once the view is manually updated to the new configuration. Using a custom config spec seems to make no difference (though I'm no expert on config specs).

The project POM includes the following lines:
<scm>
<connection>scm:clearcase:no_spec</connection>
</scm>

The hang is caused by the 'cleartool update' command, which requires an extra argument (-force) to prevent it from displaying the following message and waiting for input:

The stream's configuration has changed.
This update operation will make the view show the new configuration.
Do you want to update the view now? [yes]

Note that this issue has caused our CruiseControl server to hang, as there does not seem to be any timeout on the scm:update operation.

A patch is attached, which fixes the problem by adding the -force argument to the cleartool command. I'll let you guys decide whether there are any other unwanted side-effects of doing this.