| How to prevent resource migration between change-sets? [message #598913] |
Fri, 28 August 2009 23:14 |
 Vladimir Grishchenko
Messages: 104
Registered: July 2009 |
Senior Member |
|
|
Opening a resource automatically adds it to the currently active tasks's
context, this makes sense but the negative side effect is that this will
also move it to the changeset of this active task in case the resource has
been previously modified in a context of another task and not yet commited
to source-control repository. This is fundamentally wrong as no changes
have been made at this point in the context of the currently active task.
Developers tend to work on several tasks before committing all changes
together. With the current behavior it becomes difficult to understand
what change belongs to what task and makes it very easy to check in more
changes than needed potentially breaking the tip. Is this the intended
behavior? Any way to prevent/change it? At least a warning?
There also seem to be a bug related to this, once a change "migrated" to a
wrong task in the sync view it stays there even if the corresponding
editor is closed (the preference to remove from context on editor close is
ON) or manually removed from its context. One must re-activate the right
task (or perhaps any task whose context contains the change) for the view
to get updated.
I'm Using Mylyn 3.2.1
|
|
|
Powered by
FUDForum. Page generated in 0.03557 seconds
] 
Search
Help
Register
Login
Home
