Preserving multiple-component vobs structure

Note that this question doesn't really have anything to do with
ClearCase, since you are just importing from the file system.

I assume you want to preserve your current component boundaries, i.e.
your components in RTC will be comp1, comp2, comp3, comp4 ?

Importing the files is easy ... you can use the scm command line "share"
command.

In Eclipse, one then uses the "load as" operation to load the component
into a user specified directory. In RTC-4.0, one will be able to use
"load rules" to automatically load components into the desired
locations. I'm assuming the same is true for Visual Studio, but we
should get confirmation from that from a Visual Studio RTC user.

Cheers,
Geoff



On 11/10/2011 4:53 AM, amitkar wrote:

Hello,

I would like to migrate a ClearCase Project to RTC SCM.
The ClearCase stream is built from several multiple-component vobs.
Let's assume the following structure:

Vob1
-->comp1
-->comp2
Vob2
-->comp3
-->comp4

During the migration I would like to map a ClearCase component to RTC
component.
Migration itself will be manually. No use of import\synchronization.
This entire project will compile and run only in this structure and
refactoring could not be done due to project size. Therefor, loading
all components under same folder (workspace\sandbox) is impossible.

What are the best practices for loading such project in VisualStudio
sandbox and in Workspace so the local copy will also show the missing
vob level?

Thank you,
Amit.

Indeed this is not a matter of specific tool, just wanted to explain my existing structure.
Is it really possible to create in Eclipse under the workspace 2 "private" folders to represent the vobs, which those folders will not be part of the SCM?
or will it be available only in 4.0?
Right now in VisualStudio the only way to do it is to create 2 seperate sandboxes and load the desired components into its sandbox.
A "piovate" folder between the sandbox and component is not allowed.

When saying automatically, does it mean there will be some kind of definition for all users who load those files? will it be defined in the stream or in the repository workspace?

Thanks,
Amit.

Note that this question doesn't really have anything to do with
ClearCase, since you are just importing from the file system.

I assume you want to preserve your current component boundaries, i.e.
your components in RTC will be comp1, comp2, comp3, comp4 ?

Importing the files is easy ... you can use the scm command line "share"
command.

In Eclipse, one then uses the "load as" operation to load the component
into a user specified directory. In RTC-4.0, one will be able to use
"load rules" to automatically load components into the desired
locations. I'm assuming the same is true for Visual Studio, but we
should get confirmation from that from a Visual Studio RTC user.

Cheers,
Geoff



On 11/10/2011 4:53 AM, amitkar wrote:

Hello,

I would like to migrate a ClearCase Project to RTC SCM.
The ClearCase stream is built from several multiple-component vobs.
Let's assume the following structure:

Vob1
-->comp1
-->comp2
Vob2
-->comp3
-->comp4

During the migration I would like to map a ClearCase component to RTC
component.
Migration itself will be manually. No use of import\synchronization.
This entire project will compile and run only in this structure and
refactoring could not be done due to project size. Therefor, loading
all components under same folder (workspace\sandbox) is impossible.

What are the best practices for loading such project in VisualStudio
sandbox and in Workspace so the local copy will also show the missing
vob level?

Thank you,
Amit.

Note: My comment about it not being a ClearCase related question was
actually for our Visual Studio experts ... just to make sure they
understood it was a Visual Studio question, and not a ClearCase question
(I understood that you knew this :-).

And WRT Eclipse, yes, in 3.0 you can use the "Load As" command to load
the components in non-shared directories below the sandbox root
directory. And yes, by automatically, I do mean that in 4.0, you will
be able to save that layout in a Load Rules file, and then anyone who
wants that layout can just tell Load to use that specific Load Rules
file (you can put that load rules file under source control, so it's
available in the repository to any user).

I'll need our Visual Studio experts to comment on what is possible in
the 3.* releases, and what will be possible in the 4.0 release.

Cheers,
Geoff

On 11/10/2011 2:38 PM, amitkar wrote:

Indeed this is not a matter of specific tool, just wanted to explain
my existing structure.
Is it really possible to create in Eclipse under the workspace 2
"private" folders to represent the vobs, which those
folders will not be part of the SCM?
or will it be available only in 4.0?
Right now in VisualStudio the only way to do it is to create 2
seperate sandboxes and load the desired components into its sandbox.
A "piovate" folder between the sandbox and component is not
allowed.

When saying automatically, does it mean there will be some kind of
definition for all users who load those files? will it be defined in
the stream or in the repository workspace?

Thanks,
Amit.

gmclemmwrote:
Note that this question doesn't really have anything to do with
ClearCase, since you are just importing from the file system.

I assume you want to preserve your current component boundaries,
i.e.
your components in RTC will be comp1, comp2, comp3, comp4 ?

Importing the files is easy ... you can use the scm command line
"share"
command.

In Eclipse, one then uses the "load as" operation to load
the component
into a user specified directory. In RTC-4.0, one will be able to
use
"load rules" to automatically load components into the
desired
locations. I'm assuming the same is true for Visual Studio, but we

should get confirmation from that from a Visual Studio RTC user.

Cheers,
Geoff



On 11/10/2011 4:53 AM, amitkar wrote:
Hello,

I would like to migrate a ClearCase Project to RTC SCM.
The ClearCase stream is built from several multiple-component vobs.
Let's assume the following structure:

Vob1
-->comp1
-->comp2
Vob2
-->comp3
-->comp4

During the migration I would like to map a ClearCase component to
RTC
component.
Migration itself will be manually. No use of
import\synchronization.
This entire project will compile and run only in this structure and
refactoring could not be done due to project size. Therefor,
loading
all components under same folder (workspace\sandbox) is impossible.

What are the best practices for loading such project in
VisualStudio
sandbox and in Workspace so the local copy will also show the
missing
vob level?

Thank you,
Amit.

Note: My comment about it not being a ClearCase related question was
actually for our Visual Studio experts ... just to make sure they
understood it was a Visual Studio question, and not a ClearCase question
(I understood that you knew this :-).

And WRT Eclipse, yes, in 3.0 you can use the "Load As" command to load
the components in non-shared directories below the sandbox root
directory. And yes, by automatically, I do mean that in 4.0, you will
be able to save that layout in a Load Rules file, and then anyone who
wants that layout can just tell Load to use that specific Load Rules
file (you can put that load rules file under source control, so it's
available in the repository to any user).

I'll need our Visual Studio experts to comment on what is possible in
the 3.* releases, and what will be possible in the 4.0 release.

Cheers,
Geoff

Whatever Geoff mentioned about RTC Eclipse client holds good for visual studio client too. In RTC 4.0 for visual studio client, you should be able to use "Load Rules", and in 3.x, "Load As" command can be used.

Geoff, when you say "load rules", do you mean similar accurev load rules. www.accurev.com

The RTC-4.0 load rules are an enhancement to RTC-3.0 load rules:
https://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.help.common.jazz.calm.doc/topics/r_scm_build_loadrules.html

Cheers,
Geoff

On 11/11/2011 9:38 PM, gsokhi wrote:

Geoff, when you say "load rules", do you mean similar
accurev load rules. www.accurev.com

when you say "load rules", do you mean similar accurev load rules. www.accurev.com

Here's a visual example of what's new in RTC 4.0 related to load rules.
https://jazz.net/downloads/rational-team-concert/milestones/3.5M3?p=news#generateloadrule

Note: My comment about it not being a ClearCase related question was
actually for our Visual Studio experts ... just to make sure they
understood it was a Visual Studio question, and not a ClearCase question
(I understood that you knew this :-).

And WRT Eclipse, yes, in 3.0 you can use the "Load As" command to load
the components in non-shared directories below the sandbox root
directory. And yes, by automatically, I do mean that in 4.0, you will
be able to save that layout in a Load Rules file, and then anyone who
wants that layout can just tell Load to use that specific Load Rules
file (you can put that load rules file under source control, so it's
available in the repository to any user).

I'll need our Visual Studio experts to comment on what is possible in
the 3.* releases, and what will be possible in the 4.0 release.

Cheers,
Geoff

Whatever Geoff mentioned about RTC Eclipse client holds good for visual studio client too. In RTC 4.0 for visual studio client, you should be able to use "Load Rules", and in 3.x, "Load As" command can be used.

I've tested this with 3.0.1 and those are the results:
Eclipse works just fine and allows creating non shared folders in the workspace and loading components under those folders. VisualStudio did not allow that action - what he tried to do when loading a component with "Load As" under a non shared folder inside a sandbox is creating a new sandbox out of this folder, which ends up with an error. Maybe this is applicable with a newer version?

Regards,
Amit.

Note: My comment about it not being a ClearCase related question was
actually for our Visual Studio experts ... just to make sure they
understood it was a Visual Studio question, and not a ClearCase question
(I understood that you knew this :-).

And WRT Eclipse, yes, in 3.0 you can use the "Load As" command to load
the components in non-shared directories below the sandbox root
directory. And yes, by automatically, I do mean that in 4.0, you will
be able to save that layout in a Load Rules file, and then anyone who
wants that layout can just tell Load to use that specific Load Rules
file (you can put that load rules file under source control, so it's
available in the repository to any user).

I'll need our Visual Studio experts to comment on what is possible in
the 3.* releases, and what will be possible in the 4.0 release.

Cheers,
Geoff

Whatever Geoff mentioned about RTC Eclipse client holds good for visual studio client too. In RTC 4.0 for visual studio client, you should be able to use "Load Rules", and in 3.x, "Load As" command can be used.

I've tested this with 3.0.1 and those are the results:
Eclipse works just fine and allows creating non shared folders in the workspace and loading components under those folders. VisualStudio did not allow that action - what he tried to do when loading a component with "Load As" under a non shared folder inside a sandbox is creating a new sandbox out of this folder, which ends up with an error. Maybe this is applicable with a newer version?

Regards,
Amit.


Hi,
Can you please try this:
Suppose you have a sandbox S, and you want to load components C1 in workspace W1, and C2 in workspace W2 in a different place. Suppose you want to load components in C:\Load. So you can do a "load as" on W1/C1, and load it in C:\Load with relative path C1. Files get loaded in C:\Load\C1. Similarly you can load W2/C2 under C:\Load with relative path C2. So the files get loaded under path C:\L\C2.

Does this solve your problem?

Thank you,
That was very useful.

Regards,
Amit.