How to resolve false gaps when accepting baselines?
I try to accept baselines in eclipse. Most are empty some contain some change sets in addition to those that are already in my repository workspace. When I just try to accept all or even just a single baseline then the eclipse RTC client tells me that the action would introduce gaps, but without the option to accept all or merge! I think that dialog was popping up on my first attempt and I selected that it should just accept everything, but it did not work then. Since then I just get the error dialog without any options.
In the meantime I just expanded all the baselines and accepted all change sets one by one. That worked! So my repository workspace now does not miss any single change set of the stream anymore!
But still, when I try to accept the baselines, then I get that weird error message.
I once had the same issue before and just opened the repository workspace within another instance of eclipse, without to load that workspace there. I just opened the pending changes view for that repository workspace, accepted all changes into the unloaded repository workspace and it worked fine. In my main eclipse I then just had to reload the projects again, because it believed that now things were out of sync. I never loaded the repo workspace in the other eclipse but, well that workaround worked fine.
But now not even the workaround works anymore!
Could anyone please tell me how I can accept the empty base lines such that I do not need to collect the missing baselines in my pending changes view forever?
2 answers
Now with a little time elapsed everything works again.
There now was 1 additional change set. That change set was NOT part of any of the baselines that I tried to accept at the beginning. Actually that change set was not part of any baseline at all so far (at least none that was visible in my pending changes)! However, after I accepted that one, everything worked fine.
I do not understand why. And this is not the first time that such strange things happen to me. Is there some strange caching implemented? Might that cache get invalidated after some time, perhaps when a connections gets initialized again internally?
Whatever, I can continue to work now, so I am happy :-)