In RTC-1.0, there were limitations on how you could control the
pathnames under which files can be loaded into Jazz SCM, but those
limitations have been removed in RTC-2.0.

But there might be things we can do before then (i.e. before you upgrade
to RTC-2.0). In particular:
- What are your current list of sync roots (to find them, execute the
"select files to synchronize" operation, and click on "show existing
roots").
- What would you like them to be named?

Cheers,
Geoff

Mervyn Keene wrote:

When we first got started with RTC, I took an Eclipse Java project which
was versioned in ClearCase and imported it into Jazz source control by
the simple method of right clicking and choosing Team > Share > Jazz
source control.

At this point, we're happy with RTC and want to continue using it but we
still have a need to track the changes in CC. So I set up the ClearCase
connector successfully. The problem is that the paths don't match. In
other words the files were originally imported into RTC with paths
relative to the base of the project, while they arrived via the
connector with the vob tag prepended. Thus the same logical file seems
to be called foo\Bar.java in one stream and VOBTAG\foo\Bar.java in the
other.

Does anybody know what I can do about this mismatch?

Thanks,
MK

To avoid a variety of scenarios that are likely to confuse a user, we
require that the "component relative" pathnames in the two repositories
(CC and RTC) be the same. For non-UCM ClearCase, a "VOB" is a "component".

Note that this statement isn't quite true in RTC-1.0 (to workaround file
area loading constraints), but those constraints have been removed in
RTC-2.0, so the above statement is true in all cases in RTC-2.0.

But note that this is a statement about pathnames "in the repository".
In RTC-2.0, you are given very flexible ways of loading from the
repository into the file system, so even though the RTC repository has
the VOB segment name in it, when you load those RTC repository files
into the file system, you can load just the subtree below the VOB prefix
(or any other subtree from the RTC repository that you prefer).

Cheers,
Geoff

Mervyn.Keene wrote:

Geoff,

Thanks for the quick response. I'm headed out of town and may not be
able to answer the first question for a few days but wrt the second:
since the VOB tag is strictly a CC artifact, we would prefer not to
see it in RTC. In other words we want RTC users to think of
components and projects and resources, not paths within a VOB.

MK