When you attempt to commit a set of files Tasktop Dev/Mylyn will automatically populate the commit dialog with tasks that were active when you changed these files.In the above example you can see that the file Abstract Task is the only file in this change set and that bug 5256 was active when it was changed.All source code was written for a reason, but when viewing a particular file the original reasoning is not always clear.
The developer in charge of that component will review the patch and either apply it or ask for improvements.
The process of creating, reviewing, applying, and reapplying a patch is painless with Tasktop Dev.
A great technique for discovering the most useful tools in Eclipse is to watch an experienced developer work.
In this post Ill be sharing my change set toolset knowledge, gained from watching others, in hopes of eliminating unnecessary clicks and frustration from your workday.
Viewing the task has several advantages for understanding a particular line of code.
In the open source community developers often need to submit a patch, essentially a change set, to address a particular bug.
Thus, when you have completed a task it is easy to commit only the relevant code.
Open the Synchronize View, right-click on the change set, and select Commit.
To establish a connection between this change set and your task simply do not erase the commit message.
Later, when viewing the changed lines in file Abstract Task it will be easy to trace back to the relevant task (discussed below). They can use the following variables as well as any text to alter the commit message.
Starting from a source file, use the context menu in the editor to select Team - Show Annotations.