Can't accept active changesets from another workspace.
I made changes to some code using workspace A connected to Flow Stream S. I checked-in (not delivered) those changes and then went home. On my home machine using workspace B also connected to S, I decided that I wanted to do some more work on the pending changes just checked-in from A. So, I set my flow stream of B to point to workspace A. The pending change set from A was now visible from B but when I try to accept it I get the following error:
Active change sets cannot be accepted. Please complete the change sets or contact their owner. I know it's telling me to deliver my changes from A but I don't want to deliver them to S yet because they are not yet ready. I was hoping to finish them from B and then deliver them to S this weekend. Completing or testing half baked work done on one machine using another machine is an incredible common workflow for a developer (especially when you are trying to test some changes on a different platform.) In svn I would just have a branch for my unfinished/untested changes and then pull them into wherever I wanted to. Why is doing something similar on RTC so hard? |
12 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Apr 05 '12, 12:00 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
It sounds like the client from which you tried to do the Accept was caching the "incomplete" status, and neglected to go back to the server and notice that the change set was now complete. If you did the "complete" operation in the same Eclipse instance as you did the "accept" operation, then I'd be surprised that this would happen ... if they were different Eclipse instances, then I wouldn't be (:-). To verify this is the case, shut down and restart your Eclipse instance, and try the operation again.
Cheers, Geoff I tried this option of accepting the incomplete chageset did not work for me in RTC 2.0 |
Ralph Schoon (63.5k●3●36●46)
| answered Apr 05 '12, 6:10 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi,
this has not changed really between 2.x and 3.x. The trick mentioned above to share incomplete change sets was, as I understand, not to accept changes into another workspace (which is prevented as discussed in this thread if the change set is not completed). Instead, you can load the same repository workspace on another machine or in another Eclipse workspace. This will load the incomplete change sets too. You can continue to work with the change set which is not completed As stated, the caveat with this is that the other repository workspace loaded somewhere else will detect the difference between the local data and the changes to the not completed change set on the server and complain about it unless you synchronize the loaded workspace with the repository workspace. I tried this option of accepting the incomplete chageset did not work for me in RTC 2.0 |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.