can't open Baseline of component replicated through Distributed SCM
Scenario: Some components are replicated from server A to server B. Now in the Server B, not able to access the baselines of component which were created in the server A.
When user tries to access the Baseline of Component , promoted with below message in Change Explorer view An occur occurred while updating this part. The part's contents may be out of date and need to be refreshed. check your log for details. In the Error Log view getting below exception: java.lang.IllegalArgumentException at com.ibm.team.scm.client.internal.WorkspaceManager.getBaselineConnection(WorkspaceManager.java:1000) at com.ibm.team.scm.client.internal.WorkspaceManager.getBaselineConnection(WorkspaceManager.java:975) at com.ibm.team.filesystem.client.internal.namespace.BaselineNamespace.getConnection(BaselineNamespace.java:88) at com.ibm.team.filesystem.client.internal.namespace.BaselineNamespace.createContext(BaselineNamespace.java:98) at com.ibm.team.filesystem.client.internal.namespace.ItemNamespace.getContext(ItemNamespace.java:190) at com.ibm.team.filesystem.client.internal.snapshot.NamespaceSetContext.create(NamespaceSetContext.java:80) at com.ibm.team.filesystem.client.internal.snapshot.NamespaceSetId.createSnapshot(NamespaceSetId.java:87) at com.ibm.team.filesystem.client.internal.snapshot.SnapshotId.getSnapshot(SnapshotId.java:55) at com.ibm.team.filesystem.rcp.core.internal.rest.util.SyncViewDTOUtil.computeComparisonName(SyncViewDTOUtil.java:1741) at com.ibm.team.internal.filesystem.ui.views.structuralchanges.SnapshotCompareInput.computeName(SnapshotCompareInput.java:54) at com.ibm.team.internal.filesystem.ui.views.structuralchanges.StructuralChangesView$17.repositoryRun(StructuralChangesView.java:566) at com.ibm.team.repository.rcp.ui.operations.RepositoryOperation.run(RepositoryOperation.java:43) at com.ibm.team.repository.rcp.ui.operations.LoggedInRunner$QueuedOperation.run(LoggedInRunner.java:64) at com.ibm.team.repository.rcp.ui.operations.RetryQueue.run(RetryQueue.java:146) at com.ibm.team.repository.rcp.ui.operations.RetryQueue.access$0(RetryQueue.java:124) at com.ibm.team.repository.rcp.ui.operations.RetryQueue$1.run(RetryQueue.java:42) at com.ibm.team.repository.rcp.ui.operations.JobRunner.run(JobRunner.java:240) at com.ibm.team.repository.rcp.ui.operations.JobRunner$1.run(JobRunner.java:63) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) |
One answer
Ralph Schoon (62.0k●3●36●43)
| answered Mar 15 '16, 11:56 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I would like to suggest to open a PMR with support. If the baseline is available on the component in the repository, it should be possible to access it.
Comments when we checked line 1000 in the Work space Manager class, function is checking the Baseline is complete or not.
I don't. A baseline is immutable, so I don't know why it could be not complete. A change set can be not complete and must be completed to be delivered.
@ Ralph Schoon Forgot to mention that Replication of components from Server A( 5.0.2) to Server B (6.0.1) happened. Usually the servers would throw errors, if this is not a supported combination. In general you should only replicate between the same version of servers. But an exception should be thrown if they aren't.
|