It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787
×11,924

question asked: Aug 01 '13, 2:57 p.m.
question was seen: 4,895 times
last updated: Aug 07 '13, 1:47 a.m.

Related questions

FAQ - How this Forum works

In RTC 4.0.3 how do I load a component beneath another component.

0
Philip Molloy (3●2●3) | asked Aug 01 '13, 2:57 p.m.
 I have 5 components.  in my sandbox one of these components must load below another.
Example: Component Common_Code_II must appear as a folder under another component named Src.
In the filesystem one would see this:
./Development
./Release
./SQLServer
./Src/Common_Code_II

All five of these folders are components.
I have the following loadrule file that I thought should work.  However I get messages that /Src and /Common_Code_II are no longer in components Src and Common_Code_II and cannot be loaded into the sandbox.

loadrule:
<?xml version="1.0" encoding="UTF-8"?><!--Built from the sandbox "D:\RTC_AXCELIS\ws\import" and the workspace "OXE_Main_Workspace"--><!--Generated: 2013-08-01 14.13.36--><scm:sourceControlLoadRule xmlns:scm="http://com.ibm.team.scm" eclipseProjectOptions="import" version="1">
    <itemLoadRule alternateName="SQLServer">
        <component name="SQLServer"/>
        <!-- <component itemId="_5bPRsPrDEeKtHIO8IoHUbA" /> -->
        <item repositoryPath="/"/>
        <!-- <item itemType="folder" itemId="_5bPRtPrDEeKtHIO8IoHUbA" /> -->
    </itemLoadRule>
    <itemLoadRule alternateName="Development">
        <component name="Development"/>
        <!-- <component itemId="_v6cQ4PrDEeKtHIO8IoHUbA" /> -->
        <item repositoryPath="/"/>
        <!-- <item itemType="folder" itemId="_v6cQ5PrDEeKtHIO8IoHUbA" /> -->
    </itemLoadRule>
    <itemLoadRule alternateName="Release">
        <component name="Release"/>
        <!-- <component itemId="_2HgQEPrDEeKtHIO8IoHUbA" /> -->
        <item repositoryPath="/"/>
        <!-- <item itemType="folder" itemId="_2HgQFPrDEeKtHIO8IoHUbA" /> -->
    </itemLoadRule>
    <parentLoadRule>
        <component name="Src"/>
        <parentFolder repositoryPath="/Src"/>
        <sandboxRelativePath pathPrefix = "/Src/"/>
    </parentLoadRule>
    <parentLoadRule>
        <component name="Common_Code_II"/>
        <parentFolder repositoryPath="/Common_Code_II/"/>
        <sandboxRelativePath pathPrefix="/Src/Common_Code_II"/>
    </parentLoadRule>
</scm:sourceControlLoadRule>

Any help would be appreciated.
Phil

2 answers

Most liked answers ↓|Newest answers|Oldest answers

0
permanent link
Abraham Sweiss (2.4k●13●31) | answered Aug 06 '13, 9:17 p.m.
edited Aug 06 '13, 9:18 p.m.
Phil ,

In the following article see the section, "Loading into a specific folder structure"
https://jazz.net/library/article/1016
Let us know if this helps. 

In the RFE, the team that had openned it got around the constraint by using links.  Is this something you would be interested in investigating if the above article does not provide a suitable work around.



Comments
Geoffrey Clemm commented Aug 07 '13, 1:47 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Note that this article states:
"The path to the item can not be a shared folder (if it is, it will be considered an overlap error situation). "
In other words, you cannot nest an item from one component below a folder from another component.
I agree that symbolic links are currently the workaround for achieving this kind of nesting.

1
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Aug 01 '13, 5:01 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Currently, I believe you cannot load a component below another component.  Work item Allow files/folder from one component to be loaded into a folder of a different component (164956) requests that you be able to do so.  Please feel free to add a comment to that work item indicating your interest/support.

Comments
Philip Molloy commented Aug 02 '13, 9:48 a.m. | edited Aug 02 '13, 4:09 p.m.

 Well the Account rep that is working with us has gotten this to work before on our system but for some reason we can't get it working now.  Sad.

Geoffrey Clemm commented Aug 02 '13, 4:11 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

If you get it working again, please post a follow-up.

Philip Molloy commented Aug 02 '13, 4:14 p.m. | edited Aug 02 '13, 4:22 p.m.

 Trust me I will!

It's basically stopping our entire transfer from ClearCase to RTC.
Phil

Tim Mok commented Aug 02 '13, 4:24 p.m.
JAZZ DEVELOPER

I don't know how you would have done this before but it is definitely not supported. My suggestion would be to use symbolic links.

Geoffrey Clemm commented Aug 02 '13, 4:33 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Philip: You must not have been using UCM, right?  UCM, like RTC, does not allow components to be nested, although base ClearCase of course lets you do whatever you want :-).

Philip Molloy commented Aug 06 '13, 9:29 a.m. | edited Aug 07 '13, 12:02 a.m.

 IBM service finally reported back to me that what I'm trying to do is not supported.  Despite the fact that we had it working at one time.

Also we are currently using UCM and we have many components beneath another component.  Not something I would have setup but something I inherited.
Up a creek without a paddle.
Phil

Geoffrey Clemm commented Aug 07 '13, 12:08 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

According to the ClearCase UCM manual page on mkcomp, the root directory of components cannot be nested beneath other components:
"A component's root directory must be the VOB's root directory or one level beneath it."
( http://publib.boulder.ibm.com/infocenter/cchelp/v8r0m0/index.jsp?topic=/com.ibm.rational.clearcase.cc_ref.doc/topics/ct_mkcomp.htm )
Perhaps if you can describe how this is being handled in ClearCase UCM, there might be an analogous way to handle it in RTC.


showing 5 of 7 show 2 more comments

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.