Community
Participate
Working Groups
On an old workspace, an old synchronization ended up with then name "CVS ()". The most likely cause was the removal of the project or projects that were synced. It may be the case that arestart is needed to get the empty description. This was witnessed on an old sync but we should also test to see if it happens with the model sync.
I cannot reproduce the problem. But I noticed, that after the deletion of a single last project, action CVS(projectname) is accessible and the sync view has the caption CVS(projectname).
Is what you say in comment 1 still true after a restart?
Yes.
That sounds acceptable.
But why acceptable? Isnt it a bug, that after project deletion there is still an action CVS(projectname)?
Good point. Reopening. Can you investigate the auto-removal of a Synchronize page that has no resources?
This does not seem to be trivial: ISynchronizeParticipant descendants are using ResourceDiffTree. And in the javadoc for that class is stated: For efficiency reasons, the tree only provides diffs for resources that have changes. Resources that do not contain a change but are returned from the tree will contain children in the set. I do not see reference from participant to resources - and it seems, that this reference (at least tree root) is necessary to verification if there is no changes or no resources. If this reference will be solved, then it is possible to add participant verification on syncview creation and listener to the workspace, that will verify participants on fly.
Actually, the input to a ModelSynchronizeParticipant is defined by the scope (ISynchronizationScope) of the context (ISynchronizationContxt). The input to a SubscriberParticipant is defined by a scope. Given that this is participant dependant, having code to perform an auto-remove is a bit tricky. Given that this issue is not critical, lets defer it.
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.
