Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Mylyn » "Open corresponding task" and local tasks
"Open corresponding task" and local tasks [message #18752] Tue, 24 July 2007 13:32 Go to next message
Eclipse UserFriend
Originally posted by: mauro.molinari.cardinis.com

Hello,
I have a question about the "open corresponding task" feature for local
tasks.
The question is this: should this feature work? Under which conditions?

I'll explain better. I was working on a local task and I changed some
files. Then, I went to commit the corresponding change set and the
suggested comment was:

task 1: <task name>

I removed the prefix "task 1:" because I didn't like it to be shown in
the CVS repository and committed.
Then, I immediately looked at the CVS history of one of the involved
files, located its last revision and did right click->open corresponding
task: Mylyn said it couldn't match any task...
So, I supposed the problem was the fact I removed the "task 1:" prefix.

Then, I made another try: this time I left the "task x:" prefix, but
added some other lines in the commit comment, after the "<task name>" part.
Again, immediately after the commit operation, Mylyn couldn't open the
task corresponding to the last revision of one of the involved files.

Why? What was wrong this time? Must the commit comment be EXACTLY THE
SAME as the task name (+ the prefix "task x:")? If so, isn't it too much
strict?

Thanks in advance,
Mauro.
Re: "Open corresponding task" and local tasks [message #18905 is a reply to message #18752] Wed, 25 July 2007 05:38 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: beatmik.acm.org

Yup, in general if you edit anything about the way the task is written
out you may lose the ability for Open Corresponding Task to work because
we first match on the pattern that's used. This is especially true for
local tasks where the fall back of matching on the task's URL doesn't
work. So instead of editing manually change the template via
Preferences->Mylyn->Team (fyi, that's the template that's used to
generate the regexp for the matching).

Mik

Mauro Molinari wrote:
> Hello,
> I have a question about the "open corresponding task" feature for local
> tasks.
> The question is this: should this feature work? Under which conditions?
>
> I'll explain better. I was working on a local task and I changed some
> files. Then, I went to commit the corresponding change set and the
> suggested comment was:
>
> task 1: <task name>
>
> I removed the prefix "task 1:" because I didn't like it to be shown in
> the CVS repository and committed.
> Then, I immediately looked at the CVS history of one of the involved
> files, located its last revision and did right click->open corresponding
> task: Mylyn said it couldn't match any task...
> So, I supposed the problem was the fact I removed the "task 1:" prefix.
>
> Then, I made another try: this time I left the "task x:" prefix, but
> added some other lines in the commit comment, after the "<task name>" part.
> Again, immediately after the commit operation, Mylyn couldn't open the
> task corresponding to the last revision of one of the involved files.
>
> Why? What was wrong this time? Must the commit comment be EXACTLY THE
> SAME as the task name (+ the prefix "task x:")? If so, isn't it too much
> strict?
>
> Thanks in advance,
> Mauro.
Re: "Open corresponding task" and local tasks [message #18949 is a reply to message #18905] Wed, 25 July 2007 07:16 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: mauro.molinari.cardinis.com

Mik Kersten ha scritto:
> Yup, in general if you edit anything about the way the task is written
> out you may lose the ability for Open Corresponding Task to work because
> we first match on the pattern that's used. This is especially true for
> local tasks where the fall back of matching on the task's URL doesn't
> work. So instead of editing manually change the template via
> Preferences->Mylyn->Team (fyi, that's the template that's used to
> generate the regexp for the matching).
>
> Mik

I see, thank you Mik.

But wouldn't it better to make an inclusion match of the template within
the CVS commit instead of an exact match? I say this because it is often
useful to add some more details in the CVS comment after working on
something, because you may want to add some more information about what
you did. This kind of information is dynamic (so it's not the case of
editing the commit template in the preferences) and in order to achieve
the same result you should change the task name, including the
details... not so "elegant", I think...

Changing the behaviour in this way of course might cause the
corresponding task search operation to hit more than one result: in this
case Mylyn may use the search view to display all the results, while
marking as "potential matches" those tasks that do not match exactly the
commit template.

What do you think about it?

Mauro.
Re: "Open corresponding task" and local tasks [message #20903 is a reply to message #18949] Sat, 28 July 2007 01:55 Go to previous message
Eclipse UserFriend
Originally posted by: beatmik.acm.org

It could be possible to do it based on an inclusion, and we do have a
fall-back strategy. But note that we dynamically generate a regexp from
what you enter, so dynamically generating custom inclusion strategies
would be getting pretty complicated and unless we have indication that
it's needed for common it isn't likely to become a priority. The
current regexp generation was actually a community contribution, so if
anyone needs this support we could take enhancements to it as patches.

Mik

Mauro Molinari wrote:
> But wouldn't it better to make an inclusion match of the template within
> the CVS commit instead of an exact match? I say this because it is often
> useful to add some more details in the CVS comment after working on
> something, because you may want to add some more information about what
> you did. This kind of information is dynamic (so it's not the case of
> editing the commit template in the preferences) and in order to achieve
> the same result you should change the task name, including the
> details... not so "elegant", I think...
>
> Changing the behaviour in this way of course might cause the
> corresponding task search operation to hit more than one result: in this
> case Mylyn may use the search view to display all the results, while
> marking as "potential matches" those tasks that do not match exactly the
> commit template.
>
> What do you think about it?
Re: "Open corresponding task" and local tasks [message #574879 is a reply to message #18752] Wed, 25 July 2007 05:38 Go to previous message
Mik Kersten is currently offline Mik KerstenFriend
Messages: 287
Registered: July 2009
Senior Member
Yup, in general if you edit anything about the way the task is written
out you may lose the ability for Open Corresponding Task to work because
we first match on the pattern that's used. This is especially true for
local tasks where the fall back of matching on the task's URL doesn't
work. So instead of editing manually change the template via
Preferences->Mylyn->Team (fyi, that's the template that's used to
generate the regexp for the matching).

Mik

Mauro Molinari wrote:
> Hello,
> I have a question about the "open corresponding task" feature for local
> tasks.
> The question is this: should this feature work? Under which conditions?
>
> I'll explain better. I was working on a local task and I changed some
> files. Then, I went to commit the corresponding change set and the
> suggested comment was:
>
> task 1: <task name>
>
> I removed the prefix "task 1:" because I didn't like it to be shown in
> the CVS repository and committed.
> Then, I immediately looked at the CVS history of one of the involved
> files, located its last revision and did right click->open corresponding
> task: Mylyn said it couldn't match any task...
> So, I supposed the problem was the fact I removed the "task 1:" prefix.
>
> Then, I made another try: this time I left the "task x:" prefix, but
> added some other lines in the commit comment, after the "<task name>" part.
> Again, immediately after the commit operation, Mylyn couldn't open the
> task corresponding to the last revision of one of the involved files.
>
> Why? What was wrong this time? Must the commit comment be EXACTLY THE
> SAME as the task name (+ the prefix "task x:")? If so, isn't it too much
> strict?
>
> Thanks in advance,
> Mauro.
Re: "Open corresponding task" and local tasks [message #574941 is a reply to message #18905] Wed, 25 July 2007 07:16 Go to previous message
Mauro Molinari is currently offline Mauro MolinariFriend
Messages: 285
Registered: July 2009
Senior Member
Mik Kersten ha scritto:
> Yup, in general if you edit anything about the way the task is written
> out you may lose the ability for Open Corresponding Task to work because
> we first match on the pattern that's used. This is especially true for
> local tasks where the fall back of matching on the task's URL doesn't
> work. So instead of editing manually change the template via
> Preferences->Mylyn->Team (fyi, that's the template that's used to
> generate the regexp for the matching).
>
> Mik

I see, thank you Mik.

But wouldn't it better to make an inclusion match of the template within
the CVS commit instead of an exact match? I say this because it is often
useful to add some more details in the CVS comment after working on
something, because you may want to add some more information about what
you did. This kind of information is dynamic (so it's not the case of
editing the commit template in the preferences) and in order to achieve
the same result you should change the task name, including the
details... not so "elegant", I think...

Changing the behaviour in this way of course might cause the
corresponding task search operation to hit more than one result: in this
case Mylyn may use the search view to display all the results, while
marking as "potential matches" those tasks that do not match exactly the
commit template.

What do you think about it?

Mauro.
Re: "Open corresponding task" and local tasks [message #576025 is a reply to message #18949] Sat, 28 July 2007 01:55 Go to previous message
Mik Kersten is currently offline Mik KerstenFriend
Messages: 287
Registered: July 2009
Senior Member
It could be possible to do it based on an inclusion, and we do have a
fall-back strategy. But note that we dynamically generate a regexp from
what you enter, so dynamically generating custom inclusion strategies
would be getting pretty complicated and unless we have indication that
it's needed for common it isn't likely to become a priority. The
current regexp generation was actually a community contribution, so if
anyone needs this support we could take enhancements to it as patches.

Mik

Mauro Molinari wrote:
> But wouldn't it better to make an inclusion match of the template within
> the CVS commit instead of an exact match? I say this because it is often
> useful to add some more details in the CVS comment after working on
> something, because you may want to add some more information about what
> you did. This kind of information is dynamic (so it's not the case of
> editing the commit template in the preferences) and in order to achieve
> the same result you should change the task name, including the
> details... not so "elegant", I think...
>
> Changing the behaviour in this way of course might cause the
> corresponding task search operation to hit more than one result: in this
> case Mylyn may use the search view to display all the results, while
> marking as "potential matches" those tasks that do not match exactly the
> commit template.
>
> What do you think about it?
Previous Topic:Simplest integration with ClearCase
Next Topic:I have seen references to sub-tasks...
Goto Forum:
  


Current Time: Wed Jun 03 01:42:56 GMT 2020

Powered by FUDForum. Page generated in 0.02155 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top