| How to prevent resource migration between change-sets? [message #482992] |
Fri, 28 August 2009 19:14  |
Eclipse User |
|
|
|
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
|
|
|
|
|
|
| Re: How to prevent resource migration between change-sets? [message #485166 is a reply to message #483044] |
Thu, 10 September 2009 12:49  |
| Eclipse User |
|
|
|
After actively using Mylyn for a couple of weeks I regretfully want to
report that changeset support is somewhere between annoying and unusable.
Per my previous post and the corresponding bug changes get associated with
wrong tasks and then it is very difficult to unmarry them. "Reassign
changes to" is a hit and miss, sometimes I have to do it twice for
reassign to succeed, and occasionally it won't work no matter how hard I
try even after removing resources from the task context.
Having said that, I'm using an in house-built connector hence the
question, is this possible that the way connector is implemented is not
playing well with changesets?
|
|
|
| Re: How to prevent resource migration between change-sets? [message #598940 is a reply to message #482992] |
Sat, 29 August 2009 16:04 |
| Eclipse User |
|
|
|
Hello Vladimir,
please file a corresponding bug and add me to Cc:. I would be happy to vote on this.
Спасибо, Jörg
On 08/29/09 01:14, Vladimir Grishchenko wrote:
> 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
>
|
|
|
| Re: How to prevent resource migration between change-sets? [message #598948 is a reply to message #483039] |
Sat, 29 August 2009 18:52 |
| Eclipse User |
|
|
|
Please take a look at this bug for a related discussion:
162007: [change sets] Do not include files in change set unless edited when
task is active
https://bugs.eclipse.org/bugs/show_bug.cgi?id=162007
Steffen
Jörg Thönnes wrote:
> Hello Vladimir,
>
> please file a corresponding bug and add me to Cc:. I would be happy to
> vote on this.
>
> Спасибо, Jörg
>
> On 08/29/09 01:14, Vladimir Grishchenko wrote:
>> 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
>>
--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com
|
|
|
|
| Re: How to prevent resource migration between change-sets? [message #599062 is a reply to message #483044] |
Thu, 10 September 2009 12:49 |
| Eclipse User |
|
|
|
After actively using Mylyn for a couple of weeks I regretfully want to
report that changeset support is somewhere between annoying and unusable.
Per my previous post and the corresponding bug changes get associated with
wrong tasks and then it is very difficult to unmarry them. "Reassign
changes to" is a hit and miss, sometimes I have to do it twice for
reassign to succeed, and occasionally it won't work no matter how hard I
try even after removing resources from the task context.
Having said that, I'm using an in house-built connector hence the
question, is this possible that the way connector is implemented is not
playing well with changesets?
|
|
|
Powered by
FUDForum. Page generated in 0.47399 seconds
Home