Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

On Friday, my Rational Team Concert repository workspace was loaded in my local RTC Eclipse environment with folders on my hard drive

Today, for some reason RTC does not consider it "loaded". It is giving me a "Accepting incoming changes into a disconnected component will not load them into the sandbox. Do you want to continue?" warning when I try to accept the incoming changes, and it's not showing any outgoing changes when I refresh the filesystem.

The tetris piece representing the source control component is outlined blue (not loaded) rather than filled in blue (loaded).

Why isn't my checkout considered "loaded" anymore? How do I make it consider the workspace loaded without overwriting my local changes?

In the past, I've dealt with this situation by:

  1. Making a copy of my checkout folders
  2. Reloading them from source control
  3. Overwriting the the load wiht my backup copy

This is a time-intensive and error-prone procedure. Is there any way to make RTC just recognize the same workspace that it had before?

Tag suggestions: rtc rational-team-concert jazz

share|improve this question

2 Answers 2

up vote 3 down vote accepted

I've noticed this happen when RTC has locked itself out of it's own workspace files. Instead of reloading the entire workspace, you can try forcing a load of a single component.

1) Under "My Repository Workspaces" find your workspace, and find a small component. Right-click and Load As

2) In the Load Repository Folder dialog, it may not show any items in Sandbox (or, it may show your root source folder). If you can't find the target workspace, use Create and select the existing folder on disk, where your source was previously. Also use the same directory name for the component.

3) Hit Finish. If you had loaded this component previously, it will tell you that content is already at the destination. That's fine, overwrite it (if you had changes in there you want to keep, copy them out first).

4) After it loads the component, it should refresh its own view of the workspace, and "remember" that you had the other components loaded.

I have found this to be faster than reloading the entire workspace, since you can pick a component that will load very quickly. But you will probably have to repeat this for each workspace in order to refresh them all.

share|improve this answer

I was looking for answer to this for long time. From my purely personal opinion - I've never had do deal with so much crap like when using this tool. I can hardly believe somebody wants to get money from selling this when there are other alternatives which will at least DO the task (I'm not even targeting "do better" thing). Now - when the rage has flown through me already...

I do lots of syncing between our local git repository and client's RTC. And situation like above happens mostly when using command line lscm tool while not having eclipse opened. Seems like this part (ie. lack of eclipse) is the "disconnection" thing. Solution I've found today is:

  • close everything
  • restart your computer
  • open RTC's Eclipse FIRST
share|improve this answer
    
Absolutely agree about this "never had to deal with so much crap" part! –  Wolfram Rittmeyer Feb 10 at 15:25

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.