You only need a different repository workspace if you want to see a
different configuration (set of file states) from what is in another
repository workspace. For example, you'd have a different repository
workspace if you want to work in parallel on an earlier, later, or
different stream of development.

So in your case, you really only need one repository workspace, since
the same repository workspace can be loaded into the file area of
different Eclipse workspaces (potentially on different computers). You
would place each of your applications into it's own component, so you
can "baseline" each application separately. Also, this allows you to
decide/control which application you want to load into the file area of
a given Eclipse workspace (you are allowed to specify which components
of a given repository workspace you want to load into the file area of a
given Eclipse workspace).

Cheers,
Geoff (ClearCase Connector team)

karasiuk wrote:

I am confused about how many Repository Workspaces I need.

I like to keep each of my applications in their own workspace. I have
about 12 of them. Each application is reasonably small, on the order
of 10 projects.

I tend to work on three different computers, Home, Work and Laptop.

Do I need a different Repository Workspace for the combination of each
of my computers and each of my applications? i.e. 12x3=36 Repository
Workspaces?

Right now I just have 12 Repository Workspaces, but the way that they
share files seems odd, which makes me think that Jazz isn't meant to
work this way.

If you execute the "load" operation on the workspace, it will bring in
any changes made to that workspace by other clients. I'll see if there
is already an enhancement request to get some kind of GUI indication of
this skew, and submit one if there isn't.

Cheers,
Geoff (ClearCase Connector team)

karasiuk wrote:

Geoff, Thanks for your response.

What mechanism then keeps these Eclipse workspaces synchronized? Is
there a manual step that I have to perform?

Here is the scenario that made me wonder about this. I was working on
my desktop system making changes in a number of different projects.

The next day I switched to my laptop which already had the same
repository workspace loaded. It didn't tell me that I needed to
accept anything, but yet it didn't have the changes that I made the
day before.

I've submitted enhancement request 43282 for this functionality.

Cheers,
Geoff (ClearCase Connector team)

Geoffrey Clemm wrote:

If you execute the "load" operation on the workspace, it will bring in
any changes made to that workspace by other clients. I'll see if there
is already an enhancement request to get some kind of GUI indication of
this skew, and submit one if there isn't.

karasiuk wrote:
Geoff, Thanks for your response.

What mechanism then keeps these Eclipse workspaces synchronized? Is
there a manual step that I have to perform?

Here is the scenario that made me wonder about this. I was working on
my desktop system making changes in a number of different projects.

The next day I switched to my laptop which already had the same
repository workspace loaded. It didn't tell me that I needed to
accept anything, but yet it didn't have the changes that I made the
day before.

When you are loading the same repository workspace onto different machines, any operation which affects the file area will prompt you to re-load any "out-of-sync" projects. We use the term "out-of-sync" to mean that the file area is no longer synchronized with the repository workspace. These error dialog should allow you to re-load.