You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dave Blumenfeld (JIRA)" <ji...@codehaus.org> on 2007/02/07 03:41:44 UTC
[jira] Created: (SCM-279) Clearcase scm:update Hangs After Stream
Configuration Has Changed (patch included)
Clearcase scm:update Hangs After Stream Configuration Has Changed (patch included)
----------------------------------------------------------------------------------
Key: SCM-279
URL: http://jira.codehaus.org/browse/SCM-279
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-clearcase
Affects Versions: 1.0-beta-4
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
Reporter: Dave Blumenfeld
Priority: Critical
Attachments: ClearCaseUpdateCommand.java, DebugOutput.txt
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-279) Clearcase scm:update Hangs After Stream
Configuration Has Changed (patch included)
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse updated SCM-279:
---------------------------------
Fix Version/s: 1.0
> Clearcase scm:update Hangs After Stream Configuration Has Changed (patch included)
> ----------------------------------------------------------------------------------
>
> Key: SCM-279
> URL: http://jira.codehaus.org/browse/SCM-279
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-clearcase
> Affects Versions: 1.0-beta-4
> 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
> Reporter: Dave Blumenfeld
> Priority: Critical
> Fix For: 1.0
>
> Attachments: ClearCaseUpdateCommand.java, DebugOutput.txt, scm-clearcase-update.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-279) Clearcase scm:update Hangs After Stream
Configuration Has Changed (patch included)
Posted by "Mark Holster (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Holster updated SCM-279:
-----------------------------
Attachment: scm-clearcase-update.patch
Attatched path covers the test-cases as well.
> Clearcase scm:update Hangs After Stream Configuration Has Changed (patch included)
> ----------------------------------------------------------------------------------
>
> Key: SCM-279
> URL: http://jira.codehaus.org/browse/SCM-279
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-clearcase
> Affects Versions: 1.0-beta-4
> 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
> Reporter: Dave Blumenfeld
> Priority: Critical
> Attachments: ClearCaseUpdateCommand.java, DebugOutput.txt, scm-clearcase-update.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-279) Clearcase scm:update Hangs After Stream
Configuration Has Changed (patch included)
Posted by "Bharat Haria (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89458 ]
Bharat Haria commented on SCM-279:
----------------------------------
We have the same issue as we use Clearcase UCM and multiple teams use different streams (branches) for development and we converge in the Integration stream. Our cruisecontrol service on the integration hangs unless we patch the code using the same mechanism described above.
> Clearcase scm:update Hangs After Stream Configuration Has Changed (patch included)
> ----------------------------------------------------------------------------------
>
> Key: SCM-279
> URL: http://jira.codehaus.org/browse/SCM-279
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-clearcase
> Affects Versions: 1.0-beta-4
> 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
> Reporter: Dave Blumenfeld
> Priority: Critical
> Attachments: ClearCaseUpdateCommand.java, DebugOutput.txt, scm-clearcase-update.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-279) Clearcase scm:update Hangs After Stream
Configuration Has Changed (patch included)
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse closed SCM-279.
--------------------------------
Assignee: Emmanuel Venisse
Resolution: Fixed
Applied.
> Clearcase scm:update Hangs After Stream Configuration Has Changed (patch included)
> ----------------------------------------------------------------------------------
>
> Key: SCM-279
> URL: http://jira.codehaus.org/browse/SCM-279
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-clearcase
> Affects Versions: 1.0-beta-4
> 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
> Reporter: Dave Blumenfeld
> Assigned To: Emmanuel Venisse
> Priority: Critical
> Fix For: 1.0
>
> Attachments: ClearCaseUpdateCommand.java, DebugOutput.txt, scm-clearcase-update.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira