Community
Participate
Working Groups
Build ID: I20070625-1500 It would be much more flexible if, when trying to open the corresponding task, Mylyn did an inclusing matching with the commit template (and/or on just the task name), instead of an exact matching. This because, right now, if you alter the commit comment in any way (either because you want to add more information on what you changed or because the - usually short - task name isn't so clear to explain why you are committing something), you can't then link the CVS history entries to local tasks anymore. This might lead to more hits for a single history entry (think of tasks with similar names, for instance): in this case, Mylyn could populate the search view with all tasks matching the inclusion on the commit template.
Mauro, could you provide a concrete example to reproduce the failure?
(In reply to comment #1) > Mauro, could you provide a concrete example to reproduce the failure? Well, I actually I wasn't ever been able to make this feature working. I have a Task called "Unit test XY". I have a commit template of; ${connector.task.prefix} ${task.key}: ${task.description} ${task.url} I activated the task and made some changes. Then, I committed the change set associated with the task and leaved the default commit message of "task 39: Unit test XY". Then, whenever I do a Team | Show History for one of the changed files, select one of the cvs revisions with comment "task 39: Unit test XY" and do a right-click => "Open corresponding task", I ALWAYS get the following error: "Unable to match task. Open Repository Task dialog?". Please note that the project owning that file is associated with the Local Task Repository (through the "Task repository" preferences page), although I don't know what's this association is for. What I could think is that I noticed that Eclipse often adds a new line character at the end of the commit message, so maybe Mylyn is not able to do the match because of this. An inclusion matching would then work in this case. But, anyway, my enhancement request is not only to fix this problem, but to make the all thing work better. Suppose I change a file and commit it by modifying the commit message to something like: "task 39: Unit test XY In this specific commit I did many good things for these files" I mean, I would like to be able to add some custom comments to the default comment generated by the commit template, if I need to add some information specific to a single commit operation. This, however, will surely lead to the inability of using "Open Corresponding Task" then. Mauro.
(In reply to comment #2) > (In reply to comment #1) > Well, I actually I wasn't ever been able to make this feature working. Sorry for this terrible English... I meant: "Well, actually I wasn't ever able to make this feature work"... Mauro.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
