Community
Participate
Working Groups
If i do Team->Synchronize with repository I get an entry of that synch in my synch view. I can pin that entry so that even after a restart it still have same selection right at hand. But if i do Compare -> with version or branch i also get a entry in my synch view. I can say it must be pinned. But after a restart it is gone. This is quite annoying because this is what i do: I have 2 branches: 2.1.1 and 3.0 (head). I do all my development normally in head. But somethings can be pushed to the 2.1.1 branch. To synch the 2.1.1 branch with head i do compare with HEAD. Then i do my things and the files that are then not supposed to be merged i remove from view (because the box that is explaining remove from view says If both sides don't change it will stay hidden. And the file will come again if there are new changes, this is correct??) With that remove from view i can very easely do my synch and synch only what i want and remove what shouldn't be synched. But when i restart eclipse. That entry in my synch view is gone. Even if i said that is should be pinned. What i do find very strange is this: If i do team -> update. I get that strange select tag dialog. I still don't know why i would have that dialog there. 99,99% of the time you wouldn't select another tag to update agains. When would you?? That select other tag should be another more hidden update action in a menu. BUT that select tag dialog would be very handy with Team->synchronize with repository.. Then i could syncronize against versions..
Comparisons are not persisted between workbench sessions. Synchronizations, whether it be a sync, a compare, or a merge, decide if they can be persisted, and pinning is more of a UI hint that the sync view should replace the sync. We have thought about persisting comparisons between sessions, it isn't really all that hard, but we didn't get around to doing it. But I think there is a solution for you, instead of running a comparison against the branch you should run a merge. Merges are persisted across sessions and are three way so that you can see the outgoing/incoming changes easier. We work in this mode all the time, since we have maintenance branches. That would let you monitor the branch for changes are update the files when you want.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
