Re: [mylyn-versions-dev] Task changeset mapping

[Kilian Matt <kilian.matt@xxxxxxxxxxxxxxxxx>]

The current implementation just checks if the commit message contains
the bug-id or url.
I've already committed that to versions (versions.tasks.core versions.tasks.ui).


I was going to enhance that parsing and more store that mapping in the
workspace.

Steffen, do you have a better approach for that?

Kilian
On Fri, Feb 4, 2011 at 12:26 AM, Steffen Pingel
<steffen.pingel@xxxxxxxxxxx> wrote:
> That sounds very cool. Do you want to share the implementation on a
> bug or commit to tbr? At least the API portion of this should be in
> the Mylyn Tasks project to support usage with other providers, e.g.
> when change sets are stored in the task repositories.
>
> Steffen
>
>
> On Thu, Feb 3, 2011 at 3:20 PM, Kilian Matt
> <kilian.matt@xxxxxxxxxxxxxxxxx> wrote:
>> Hi,
>>
>> I've also implemented a rather stupid prototype for a changeset page for tasks.
>> The idea is, that all changesets of a task show up in another page of
>> the task editor.
>>
>> Again, this is only in a prototype state, as it just implements as
>> much, as I need for TBR.
>>
>> Kilian
>> _______________________________________________
>> mylyn-versions-dev mailing list
>> mylyn-versions-dev@xxxxxxxxxxx
>> http://dev.eclipse.org/mailman/listinfo/mylyn-versions-dev
>>
>
>
>
> --
> Steffen Pingel
> Committer, http://eclipse.org/mylyn
> Senior Developer, http://tasktop.com
> _______________________________________________
> mylyn-versions-dev mailing list
> mylyn-versions-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/mylyn-versions-dev
>