The Workspaces that the pending changes view tracks is managed by the
eclipse workspace preferences. You can check to see if
Preferences>Team>Jazz Source Control>Sandboxes to see if the sandbox is
being restored everytime you restart Eclipse.

Did your repository URL change? Off the top of my head that's one of the
things I can think of that would affect this.

When you have time, you can try loading and creating a second local
Eclipse workspace from the same repository workspace and see if it suffers
the same tracking problems. Maybe it will behave better if it is starting
from a fresh set of preferences. Or alternatively, you can try deleting
your preferences in your current eclipse workspace and doing a full
unload/load.



On Sat, 21 Nov 2009 11:23:00 -0500, rost
<robert> wrote:

After migration from Tomcat to WAS 7.0.0.3 Pending Changes views in
all our local workspaces are empty.

Repository is connected, I can work with work items, refreshing
Pending Changes view doesn't help, Repairing Metadata also.

The only solution is to load repository workspace again (although it
has been loaded previously, before migration), using an option: Do
not load anything. The worspace will be tracked by the Pending
Changes view.
After that, Pending Changes views is normal again (not empty), but
only for the remaining Eclipse session. After restarting Eclipse,
Pending Changes views is empty again, and whole process of loading
(without actually loading anything) has to be repeated again.

Seems like a serious bug to me.

Robert

Forgot to mention that I'm using WAS 6.1 on a Linux server

On 11/21/2009 11:23 AM, rost wrote:

After migration from Tomcat to WAS 7.0.0.3 Pending Changes views in
all our local workspaces are empty.

Repository is connected, I can work with work items, refreshing
Pending Changes view doesn't help, Repairing Metadata also.

The only solution is to load repository workspace again (although it
has been loaded previously, before migration), using an option: Do
not load anything. The worspace will be tracked by the Pending
Changes view.
After that, Pending Changes views is normal again (not empty), but
only for the remaining Eclipse session. After restarting Eclipse,
Pending Changes views is empty again, and whole process of loading
(without actually loading anything) has to be repeated again.

Seems like a serious bug to me.

Robert

I can confirm Robert's description of the problem (I'm using RTC 2.0 GA).

Reloading will temporarily fix the problem, until Eclipse is restarted.

Kind of makes multiple sandboxes unpleasant to use.

Dave


On 11/21/2009 11:23 AM, rost wrote:

After migration from Tomcat to WAS 7.0.0.3 Pending Changes views in
all our local workspaces are empty.

Repository is connected, I can work with work items, refreshing
Pending Changes view doesn't help, Repairing Metadata also.

The only solution is to load repository workspace again (although it
has been loaded previously, before migration), using an option: Do
not load anything. The worspace will be tracked by the Pending
Changes view.
After that, Pending Changes views is normal again (not empty), but
only for the remaining Eclipse session. After restarting Eclipse,
Pending Changes views is empty again, and whole process of loading
(without actually loading anything) has to be repeated again.

Seems like a serious bug to me.

Robert

Rob, or Dave,

Can you file a bug against Source Control about this?

Dave, did this also happen to you after a migration (like in Rob's case)
or did this occur out of the box?

On Sat, 21 Nov 2009 11:23:00 -0500, rost
<robert> wrote:

After migration from Tomcat to WAS 7.0.0.3 Pending Changes views in
all our local workspaces are empty.

Repository is connected, I can work with work items, refreshing
Pending Changes view doesn't help, Repairing Metadata also.

The only solution is to load repository workspace again (although it
has been loaded previously, before migration), using an option: Do
not load anything. The worspace will be tracked by the Pending
Changes view.
After that, Pending Changes views is normal again (not empty), but
only for the remaining Eclipse session. After restarting Eclipse,
Pending Changes views is empty again, and whole process of loading
(without actually loading anything) has to be repeated again.

Seems like a serious bug to me.

Robert

--

Opened Defect 100944

We've been using WAS/DB2 forever, so in my case, no migration was involved.


On 12/3/2009 9:57 AM, Andrew Hoo wrote:

Rob, or Dave,

Can you file a bug against Source Control about this?

Dave, did this also happen to you after a migration (like in Rob's case)
or did this occur out of the box?

On Sat, 21 Nov 2009 11:23:00 -0500, rost
robert.stanko@apis-it-dot-hr.no-spam.invalid> wrote:

After migration from Tomcat to WAS 7.0.0.3 Pending Changes views in
all our local workspaces are empty.

Repository is connected, I can work with work items, refreshing
Pending Changes view doesn't help, Repairing Metadata also.

The only solution is to load repository workspace again (although it
has been loaded previously, before migration), using an option: Do
not load anything. The worspace will be tracked by the Pending
Changes view.
After that, Pending Changes views is normal again (not empty), but
only for the remaining Eclipse session. After restarting Eclipse,
Pending Changes views is empty again, and whole process of loading
(without actually loading anything) has to be repeated again.

Seems like a serious bug to me.

Robert