Hi Geoff and Rupa,

This issue is seen in both clients. The users who are seeing this and mentioning it to me now are using the Eclipse client.

However, the issue appears to be this (I apologize for the lengthy post. I have documented as much as possible here to show you what I did):

If you have your sandbox for your workspaces set up as C:\Workspaces and you change it to C:\RTC, the metadata for the new sandbox is still captured under C:Workspaces (if the folder named C:Workspaces still exists). There is a way to change this using RTC.

Here is the use case:

1. Users on a team here were creating workspaces for several months under C:\RTC2.0. Most of the team was using RTC Eclipse client just fine this way. Others had C:\RTC for the workspaces path.

2. There is now a need to "Standardize" how the workspaces are setup. So they asked me about it. I said "No problem, just pick something like C:\RTC and create new workspaces under that new workspace path. It should be simple enough." So, based on that, the new standard for workspace paths was going to be "C:\RTC".

3. Most users were just going to "switch" their sandboxes from C:\RTC2.0 to C:\RTC. A couple of them were just setting up RTC for the first time and would be using C:\RTC from the start for their sandbox.

4. The users who "switched" to C:\RTC removed their existing workspaces under C:\RTC2.0 using the Unload action in RTC. Then they shut down their RTC Eclipse client. When they reopened it, they were brought to the RTC Welcome screen. This was expected (or rather "not unexpected") and I had the users log into RTC using the correct Connection URL and their RTC logins.

5. The users were able to create new workspaces under the new sandbox (C:\RTC) and continue working.

6. One of the users noticed that even though he had removed C:\RTC2.0 on his PC that it reappeared again after restarting the RTC Eclipse client. We both looked at it and noticed that there was a folder named .metadata under it. We figured that this was just some latency information that was cached and that it would eventually go away. So, the user left it there. It was not hurting anything by leaving it there. This also happened t the other users who switched from C:\RTC2.0 to C:\RTC. They also had no problem leaving the old C:\RTC2.0 folder on their PCs.

After discussing this post with Geoff I realized that the old .metadata folder is not going to go away. At least not without taking one more step.
1. In the Eclipse client, from the top menu bar select File->Switch Workspace.
2. From the drop down menu, from the list of workspace paths displayed (C:\RTC2.0 was in this list), select Other...
3. In the dialog labeled Workspace Launcher, either enter in the new Workspace folder name or Browse to it (i.e., if C:\RTC already existed).
4. In our case, users entered C:\RTC. This created a new folder named .metadata under C:\RTC. All workspaces under C:\RTC are now seen in the Pending Changes view, whether or not Incoming/Outgoing Changes are detected.
OK that was actually 4 steps. But, the end result was what our users here expect and this makes them happy.

This is just an observation on my part: Perhaps in a future release, RTC will automatically add a .metadata folder under a new workspace path. That is, when I switch from C:\RTC2.0 to C:\RTC and create new workspaces under C:\RTC a new .metadata folder will be created there without having to manually run the Workspace Launcher. I believe that the information entered in that dialog is cached and used by RTC. This is not a bad thing. I think it would be nice to be able to switch the location "on the fly".

One other thing: In the Eclipse Client, when I select Window-->Preferences->expand Team->expand Jazz Source Control and then select "Sandboxes", all of the ones on my PC do show up in the window labeled "Configure which folders are known and tracked by the Pending Changes view". When I originally reported this issue only 2 of the workspaces under one of the workspace paths (C:\RTC2.0) were displayed in the Pending Changes view. Based on what I was seeing when I originally reported this issue, I am not sure that this is working.

As I mentioned before, we also have several workspaces set up as "Do not load anything. The workspace will be tracked by the Pending Changes view" on our workstation that we do builds on. I just went on there and for several of the workspaces that I knew had Incoming Changes, I had to run the load action on them (using the Eclipse Client). To me, this is not a big issue. If there was a build request for builds using those workspaces, the build action would force "Accept Pending Changes" during the build. Most users of RTC here do not set up their workspaces with "Do not load anything. The workspace will be tracked by the Pending Changes view". So, this is also just an observation.

So, I now understand what is happening in this case and I now know how to resolve this type of issue.

I will look into the Work Item that Rupa entered. Thanks for the responses and the help. It really is appreciated.

-Walter

Hi Rupa,

In Walter's original message in this thread, he indicated he was using
the Eclipse client (all of my comments above were about the Eclipse
client).

Walter: Are your teammates also using the Eclipse client, or are they
using the VS client? (If the latter, Rupa's message probably explains
what they are seeing).

Cheers,
Geoff

sreerupa wrote:

Hi Walter,
If you do not load a workspace and just track it, the VS Client
does not save that information across sessions. From the forum
discussion, it looks like your workspace issues started after you
migrated to 2.0.0.2 iFix2 - which surprises me somewhat. Earlier, the
scm daemon used to maintain this information. Now it does not any
more, so this information needs to be maintained on the client side
preferences - something we haven't implemented yet. I'm trying to
remember when this change happened - it was definitely earlier than
2.0.0.2 iFix 2 I'd think.
If this is big pain point, we could try to get it in 2.0.0.2 iFix
3 - it'll be somewhat tight though. If not, we'll definitely address
it in 3.0.
I've opened
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/114291
to track this - please add your comments there.

regards
--Rupa

Hi Geoff,

Something that you mentioned about metadata has clicked and I am going to try something out. I am looking into it now and it looks like we also changed the sandbox location for the workspaces at around the same time (i.e., from C:\RTC2.0 to C:\RTC). So the old .metadata folder will still be around (under C:\RTC2.0). I'll let you know what I find on Monday. But, I think that this is the path to go down and see if fixing it resolves this issue.

Thanks,
-Walter

The list of workspaces appearing in the Pending Changes view of an
Eclipse workspace should be restored when you restart that Eclipse
workspace (except for exceptional cases such as were mentioned below,
e.g., immediately after a client upgrade, or if the previous shutdown
was interrupted). So if you are not seeing that behavior, that would be
a bug and should be reported.

Just to emphasize one point, if there is a workspace that does not
appear in your pending changes list, the *only* way to get it added in
is to use the "load" operation (and select the "do not load anything ...
track in pending changes view only" option, unless you also want files
to be downloaded to your local file area). So clicking on "Refresh
Sandboxes and Remote Changes" will never affect whether a workspace
appears in the Pending changes view (it just affects workspaces that are
already being tracked in the Pending changes view).

Cheers,
Geoff

wmansur wrote:

Hi Geoff,

I hear what you are saying. All I did was upgrade RTC from v2.0.0.2
to v2.0.0.2 iFix2. Currently only a few people are using the
upgraded version, myself and one or 2 other RTC users. I know that
they only have one or two workspaces. They have not mentioned this
behavior (maybe because I haven't asked them about it). I do have 2
places that I can test this out on - my laptop and a regular Dell
Workstation.

So, let me tell you what happened this morning when I logged in on my
laptop for the day.
1. I launched RTC and only 2 of my workspaces were displayed in the
Pending Changes view. Remember, I did a load action on all 9 of my
workspaces yesterday.
2. I clicked on "Refresh Sandboxes and Remote Changes" in
the Pending Changes view and still only 2 workspaces were displayed
there. These 2 workspaces did not have any Incoming Changes for
them. (This is probably related to what Geoff says below).

Here is where I am at. I don't mind "loading" workspaces
from time to time (or even all the time). But that's just me. The
RTC users here are very reluctant to change anything. We recently
upgraded to RTC v2.0.0.2 and I have them all on that version and they
are happy with it. That effort alone was like pulling teeth from a
wounded rhinoceros. Now, we have an "iFix" that I am
seeing a small issue with. Before I ask the rest of the RTC user
community here to upgrade to the iFix, I thought that I would ask out
on the forum if this is being seen by any one else. I'm still trying
to sell RTC itself to a lot of people who used to use SourceSafe.
Right now, these users do not have to "load" their
workspaces in order to see workspaces that have Incoming Changes.

So, I appreciate all the answers I have received and if it is OK with
everyone, I will open up a Work Item so that we can track this and
have a place to put up some logs to look at.

Thanks,

- Walter
gmclemmwrote:
Note that whether a particular workspace appears in the Pending
Changes
view of a particular Eclipse workspace depends only on metadata
stored
in that Eclipse workspace (which is controlled by the
"load" and
"unload" operations applied to that Eclipse workspace),
and is not
affected in any way by whether or not there happen to be incoming
changes to that workspace.

So that metadata could be affected by the client upgrade (there
sometimes is metadata changes between client versions), or can be
affected by abnormal termination of that workspace (in which case
metadata changes may not have been saved).

Cheers,
Geoff

wmansur wrote:
Hi Tim,

That is something that I will look into. I will shutdown my laptop
for the day soon and then see if this happens when I log in
tomorrow
AM and launch RTC for the first time. Once I "loaded" up
my workspaces today, they have come back in the Pending Changes
view
since then.

I have just checked for this on another workstation that had RTC
upgraded at the same time mine was. I have several workspaces on
that PC. Several of them are loaded with the "Do not load
anything. The workspace will be tracked by the Pending Changes
view" selection. Several of the workspaces are for streams
that
definitely have had changes made in them.

For one of the workspaces:
1. I did the load with "Do not load anything. The workspace
will
be tracked by the Pending Changes view" selected and accepted
the Incoming Changes that were picked up in the Pending Changes
view.
2. I did not "load" any other workspace.
3. I then shut down the RTC Eclipse client.
4. I restarted RTC Eclipse Client and the workspace I loaded in Step
1
was displayed in the Pending Changes view (a good thing).

However, several other workspaces that were created with the
"Do
not load anything. The workspace will be tracked by the Pending
Changes view" selection were not displayed in the Pending
Changes view, even though there are changes in the streams that
they
are attached to. I think that even being loaded with this
selection,
the workspaces that have changes coming in should be displayed in
the
Pending Changes view.

I'll let you know what happens with my laptop tomorrow morning when
I
start RTC up for the first time.

Thanks,
-Walter

tmokwrote:
Just so I understand, is this occurring the first time you start
RTC
after upgrading your client or every single time (same workspace,
same client version)? If it's every single time, it sounds like a
bug.
wmansurwrote:
Hi Tim,
I can do a "Load" then select "Do not load anything.
The workspace will be tracked by the Pending Changes view" and
that will make the workspace appear in the Pending Changes view.
So,
yes, that will work (and I do not have to load content to disk in
order to see incoming changes). This is good for the workstation
that we use for running builds. On my PC, I do load content to
disk.
The method above does work for those workspaces, so I don't need to
do a full "reload" on them. I still would have to go to
each workspace under "My Repository Workspaces" and do
"Load" then select "Do not load anything. The
workspace will be tracked by the Pending Changes view" for
each
workspace.
I also checked a PC with the RTC client for Visual Studio that I
upgraded last week and the same behavior is seen there.
I use RTC all day, every day. I don't recall having to do this
before.
-Walter

tmokwrote:
Hi Walter,
Do you have to load content to disk in order to see the incoming
changes? Nothing was changed in 2.0.0.2 ifix2 that would alter the
behaviour of tracking changes to a workspace. You should be able to
have a workspace in Pending Changes without loading content to
disk.
Is this something that is occurring every time you start the
client?
Perhaps the persisted data on workspaces in Pending Changes
couldn't
load some of the workspaces after the update. Loading the workspace
without loading content to disk should persist the workspaces in
Pending Changes again and hopefully everything will be back to
normal.

Hi Geoff,

I hear what you are saying. All I did was upgrade RTC from v2.0.0.2 to v2.0.0.2 iFix2. Currently only a few people are using the upgraded version, myself and one or 2 other RTC users. I know that they only have one or two workspaces. They have not mentioned this behavior (maybe because I haven't asked them about it). I do have 2 places that I can test this out on - my laptop and a regular Dell Workstation.

So, let me tell you what happened this morning when I logged in on my laptop for the day.
1. I launched RTC and only 2 of my workspaces were displayed in the Pending Changes view. Remember, I did a load action on all 9 of my workspaces yesterday.
2. I clicked on "Refresh Sandboxes and Remote Changes" in the Pending Changes view and still only 2 workspaces were displayed there. These 2 workspaces did not have any Incoming Changes for them. (This is probably related to what Geoff says below).

Here is where I am at. I don't mind "loading" workspaces from time to time (or even all the time). But that's just me. The RTC users here are very reluctant to change anything. We recently upgraded to RTC v2.0.0.2 and I have them all on that version and they are happy with it. That effort alone was like pulling teeth from a wounded rhinoceros. Now, we have an "iFix" that I am seeing a small issue with. Before I ask the rest of the RTC user community here to upgrade to the iFix, I thought that I would ask out on the forum if this is being seen by any one else. I'm still trying to sell RTC itself to a lot of people who used to use SourceSafe. Right now, these users do not have to "load" their workspaces in order to see workspaces that have Incoming Changes.

So, I appreciate all the answers I have received and if it is OK with everyone, I will open up a Work Item so that we can track this and have a place to put up some logs to look at.

Thanks,

- Walter

Note that whether a particular workspace appears in the Pending Changes
view of a particular Eclipse workspace depends only on metadata stored
in that Eclipse workspace (which is controlled by the "load" and
"unload" operations applied to that Eclipse workspace), and is not
affected in any way by whether or not there happen to be incoming
changes to that workspace.

So that metadata could be affected by the client upgrade (there
sometimes is metadata changes between client versions), or can be
affected by abnormal termination of that workspace (in which case
metadata changes may not have been saved).

Cheers,
Geoff

wmansur wrote:

Hi Tim,

That is something that I will look into. I will shutdown my laptop
for the day soon and then see if this happens when I log in tomorrow
AM and launch RTC for the first time. Once I "loaded" up
my workspaces today, they have come back in the Pending Changes view
since then.

I have just checked for this on another workstation that had RTC
upgraded at the same time mine was. I have several workspaces on
that PC. Several of them are loaded with the "Do not load
anything. The workspace will be tracked by the Pending Changes
view" selection. Several of the workspaces are for streams that
definitely have had changes made in them.

For one of the workspaces:
1. I did the load with "Do not load anything. The workspace will
be tracked by the Pending Changes view" selected and accepted
the Incoming Changes that were picked up in the Pending Changes view.

2. I did not "load" any other workspace.
3. I then shut down the RTC Eclipse client.
4. I restarted RTC Eclipse Client and the workspace I loaded in Step 1
was displayed in the Pending Changes view (a good thing).

However, several other workspaces that were created with the "Do
not load anything. The workspace will be tracked by the Pending
Changes view" selection were not displayed in the Pending
Changes view, even though there are changes in the streams that they
are attached to. I think that even being loaded with this selection,
the workspaces that have changes coming in should be displayed in the
Pending Changes view.

I'll let you know what happens with my laptop tomorrow morning when I
start RTC up for the first time.

Thanks,
-Walter

tmokwrote:
Just so I understand, is this occurring the first time you start RTC
after upgrading your client or every single time (same workspace,
same client version)? If it's every single time, it sounds like a
bug.
wmansurwrote:
Hi Tim,
I can do a "Load" then select "Do not load anything.
The workspace will be tracked by the Pending Changes view" and
that will make the workspace appear in the Pending Changes view. So,
yes, that will work (and I do not have to load content to disk in
order to see incoming changes). This is good for the workstation
that we use for running builds. On my PC, I do load content to disk.
The method above does work for those workspaces, so I don't need to
do a full "reload" on them. I still would have to go to
each workspace under "My Repository Workspaces" and do
"Load" then select "Do not load anything. The
workspace will be tracked by the Pending Changes view" for each
workspace.
I also checked a PC with the RTC client for Visual Studio that I
upgraded last week and the same behavior is seen there.
I use RTC all day, every day. I don't recall having to do this
before.
-Walter

tmokwrote:
Hi Walter,
Do you have to load content to disk in order to see the incoming
changes? Nothing was changed in 2.0.0.2 ifix2 that would alter the
behaviour of tracking changes to a workspace. You should be able to
have a workspace in Pending Changes without loading content to disk.
Is this something that is occurring every time you start the client?
Perhaps the persisted data on workspaces in Pending Changes couldn't
load some of the workspaces after the update. Loading the workspace
without loading content to disk should persist the workspaces in
Pending Changes again and hopefully everything will be back to
normal.