Importing from ClearCase into RTC: "Node'xxx' can not be selected" error when selecting files to be imported
When I do the same in other VOBs, it works well (so in principle I'm doing the right things).Node'xxx' can not be selected Cannot find a configuration for the selected resource. Please select a resource within VOB or sub-VOB component
In the "Browse For Files To Synchonize" windows, the VOBs which are working have grey (Component: <VOB name>) behind the VOB name in the browse box like shown in the attachment:
The exception stack does not help much:
javax.wvcm.WvcmException: Cannot find a configuration for the selected resource. Please select a resource within VOB or sub-VOB component at com.ibm.team.connector.scm.cc.ide.ui.wizards.importwizard.RootPathBrowserDialog$PathBrowserInfo.fetchConfigProperty(RootPathBrowserDialog.java:436) at com.ibm.team.connector.scm.cc.ide.ui.wizards.importwizard.RootPathBrowserDialog$PathBrowserLabelProvider$1.run(RootPathBrowserDialog.java:973) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
One answer
One way this can occur is if a VOB is a multi-component UCM VOB, where the components live one level down in the directory hierarchy. You can select the component root directory, but you cannot select the root directory of the VOB, because that directory is not in any component.
You would also get this behavior in a non-UCM VOB, if you have used the new "sub-vob component" functionality in RTC-4.0 (that functionality lets you declare that user-selected sub-directories in the VOB should be considered components, rather than the root directory of the VOB). To see whether someone has created sub-vob components in that VOB, check whether the attribute type com.ibm.rational.interop.ClearCase.subVOB_Component is declared in that VOB.
If neither is the case, please contact Rational Support or submit a work item on jazz.net, so they can investigate why you are seeing this behavior.
Comments
When I expand the top level folder, I can see the sub-folders - in all VOBs, independend if the 'work' or not.
But when I select the top level or any sub-folder, I get the error described.
The VOBs are no UCM VOBs.
Hi Geoff,
one question to your remark:
"You would also get this behavior in a non-UCM VOB, if you have used the new "sub-vob component" functionality in RTC-4.0 (that functionality lets you declare that user-selected sub-directories in the VOB should be considered components, rather than the root directory of the VOB). "
Does this mean, that synchronization with a VOB which is marked for "sub-vob component" is not possible or just that the section (Component=<name>) should be present at the folder / file marked with this attribute?
So that synchronization is just possible from this sub dir?
Greetings,
Simon
The latter ... i.e. you can select the root directory of the sub-vob component, or any file/folder under it. In general, you can only synchronize a ClearCase file/folder that is "in" a component, where a ClearCase component is either a UCM component, the entire VOB (for non-UCM), or a sub-VOB component (for non-UCM). So using the Browse wizard, in a VOB with sub-vob components, you would open up folders until you reach the sub-vob component root directory, where you would then see the "component" annotation on that directory.
Comments
Simon Eickel
Oct 17 '12, 9:11 a.m.Strange thing on this - some VOBs which had the Component standing there before have now no Components ...