| Integration with the History view [message #51007] |
Fri, 27 June 2008 12:08  |
 Marcelo Paternostro
Messages: 602
Registered: July 2009 |
Senior Member |
|
|
Hi,
I am starting to use Mylyn (at least trying to ;-). I am quite impressed
by the quality of the tools you guys a re providing. Congrats!
In EMF we use the following pattern when entering the comment for our
CVS commits (ignore the single quotes): '[bugzilla number] comments'
(ie, the bugzilla number in square brackets, followed by a space, and
then a text usually describing the changes on the files). So I've set
'Task>Team>Comment Template' to '[${task.key}] ${task.description}'.
My question, as hinted on the subject, is regarding "Mylin's integration
with the History view. In my workspace, the bugzilla # in this view is
not a link and I get a 'Unable to match task. Open Repository Task
dialog?' when I right click a version and hit 'Open Corresponding Task'.
Is this the expected behavior or should I be seeing a nicer integration
here ;-) ? Btw, I did set the project's task repository to Eclipse.org.
I am using Eclipse 3.4 with Mylyn 3.0 (3.0.0.v20080619-1900).
Thanks in advance,
Marcelo
|
|
|
| Re: Integration with the History view [message #51197 is a reply to message #51007] |
Fri, 27 June 2008 20:50  |
Steffen Pingel
Messages: 706
Registered: July 2009 |
Senior Member |
|
|
Hi Marcelo,
> I am starting to use Mylyn (at least trying to ;-). I am quite impressed
> by the quality of the tools you guys a re providing. Congrats!
Thanks. Great to hear that you are trying it out :).
> In EMF we use the following pattern when entering the comment for our
> CVS commits (ignore the single quotes): '[bugzilla number] comments'
> (ie, the bugzilla number in square brackets, followed by a space, and
> then a text usually describing the changes on the files). So I've set
> 'Task>Team>Comment Template' to '[${task.key}] ${task.description}'.
>
> My question, as hinted on the subject, is regarding "Mylin's integration
> with the History view. In my workspace, the bugzilla # in this view is
> not a link and I get a 'Unable to match task. Open Repository Task
> dialog?' when I right click a version and hit 'Open Corresponding Task'.
> Is this the expected behavior or should I be seeing a nicer integration
> here ;-) ? Btw, I did set the project's task repository to Eclipse.org.
The Bugzilla hyperlink detector expects a prefix ("task" or "bug") to
recognize task ids. You could file a new feature request if using "#" as a
prefix is a common convention in EMF.
I am not sure why 'Open Corresponding Task' is failing though, it should
work based on the specified commit comment template. Please file a new bug
report and we can investigate further:
http://www.eclipse.org/mylyn/bugs/
Steffen
|
|
|
|
| Re: Integration with the History view [message #51743 is a reply to message #51197] |
Wed, 02 July 2008 22:55 |
Marcelo Paternostro
Messages: 602
Registered: July 2009 |
Senior Member |
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Thank you for the quick answer! I've opened the feature request
(239376) as you've suggested.<br>
<br>
Cheers,<br>
Marcelo<br>
<br>
Steffen Pingel wrote:
<blockquote cite="mid:g43jr8$elc$6@build.eclipse.org" type="cite">
<pre wrap="">Hi Marcelo,
</pre>
<blockquote type="cite">
<pre wrap="">I am starting to use Mylyn (at least trying to ;-). I am quite impressed
by the quality of the tools you guys a re providing. Congrats!
</pre>
</blockquote>
<pre wrap=""><!---->
Thanks. Great to hear that you are trying it out :).
</pre>
<blockquote type="cite">
<pre wrap="">In EMF we use the following pattern when entering the comment for our
CVS commits (ignore the single quotes): '[bugzilla number] comments'
(ie, the bugzilla number in square brackets, followed by a space, and
then a text usually describing the changes on the files). So I've set
'Task>Team>Comment Template' to '[${task.key}] ${task.description}'.
My question, as hinted on the subject, is regarding "Mylin's integration
with the History view. In my workspace, the bugzilla # in this view is
not a link and I get a 'Unable to match task. Open Repository Task
dialog?' when I right click a version and hit 'Open Corresponding Task'.
Is this the expected behavior or should I be seeing a nicer integration
here ;-) ? Btw, I did set the project's task repository to Eclipse.org.
</pre>
</blockquote>
<pre wrap=""><!---->
The Bugzilla hyperlink detector expects a prefix ("task" or "bug") to
recognize task ids. You could file a new feature request if using "#" as a
prefix is a common convention in EMF.
I am not sure why 'Open Corresponding Task' is failing though, it should
work based on the specified commit comment template. Please file a new bug
report and we can investigate further:
<a class="moz-txt-link-freetext" href="http://www.eclipse.org/mylyn/bugs/">http://www.eclipse.org/mylyn/bugs/</a>
Steffen
</pre>
</blockquote>
</body>
</html>
|
|
|
|
| Re: Integration with the History view [message #590553 is a reply to message #51007] |
Fri, 27 June 2008 20:50 |
Steffen Pingel
Messages: 706
Registered: July 2009 |
Senior Member |
|
|
Hi Marcelo,
> I am starting to use Mylyn (at least trying to ;-). I am quite impressed
> by the quality of the tools you guys a re providing. Congrats!
Thanks. Great to hear that you are trying it out :).
> In EMF we use the following pattern when entering the comment for our
> CVS commits (ignore the single quotes): '[bugzilla number] comments'
> (ie, the bugzilla number in square brackets, followed by a space, and
> then a text usually describing the changes on the files). So I've set
> 'Task>Team>Comment Template' to '[${task.key}] ${task.description}'.
>
> My question, as hinted on the subject, is regarding "Mylin's integration
> with the History view. In my workspace, the bugzilla # in this view is
> not a link and I get a 'Unable to match task. Open Repository Task
> dialog?' when I right click a version and hit 'Open Corresponding Task'.
> Is this the expected behavior or should I be seeing a nicer integration
> here ;-) ? Btw, I did set the project's task repository to Eclipse.org.
The Bugzilla hyperlink detector expects a prefix ("task" or "bug") to
recognize task ids. You could file a new feature request if using "#" as a
prefix is a common convention in EMF.
I am not sure why 'Open Corresponding Task' is failing though, it should
work based on the specified commit comment template. Please file a new bug
report and we can investigate further:
http://www.eclipse.org/mylyn/bugs/
Steffen
|
|
|
|
| Re: Integration with the History view [message #590723 is a reply to message #51197] |
Wed, 02 July 2008 22:55 |
Marcelo Paternostro
Messages: 602
Registered: July 2009 |
Senior Member |
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Thank you for the quick answer! I've opened the feature request
(239376) as you've suggested.<br>
<br>
Cheers,<br>
Marcelo<br>
<br>
Steffen Pingel wrote:
<blockquote cite="mid:g43jr8$elc$6@build.eclipse.org" type="cite">
<pre wrap="">Hi Marcelo,
</pre>
<blockquote type="cite">
<pre wrap="">I am starting to use Mylyn (at least trying to ;-). I am quite impressed
by the quality of the tools you guys a re providing. Congrats!
</pre>
</blockquote>
<pre wrap=""><!---->
Thanks. Great to hear that you are trying it out :).
</pre>
<blockquote type="cite">
<pre wrap="">In EMF we use the following pattern when entering the comment for our
CVS commits (ignore the single quotes): '[bugzilla number] comments'
(ie, the bugzilla number in square brackets, followed by a space, and
then a text usually describing the changes on the files). So I've set
'Task>Team>Comment Template' to '[${task.key}] ${task.description}'.
My question, as hinted on the subject, is regarding "Mylin's integration
with the History view. In my workspace, the bugzilla # in this view is
not a link and I get a 'Unable to match task. Open Repository Task
dialog?' when I right click a version and hit 'Open Corresponding Task'.
Is this the expected behavior or should I be seeing a nicer integration
here ;-) ? Btw, I did set the project's task repository to Eclipse.org.
</pre>
</blockquote>
<pre wrap=""><!---->
The Bugzilla hyperlink detector expects a prefix ("task" or "bug") to
recognize task ids. You could file a new feature request if using "#" as a
prefix is a common convention in EMF.
I am not sure why 'Open Corresponding Task' is failing though, it should
work based on the specified commit comment template. Please file a new bug
report and we can investigate further:
<a class="moz-txt-link-freetext" href="http://www.eclipse.org/mylyn/bugs/">http://www.eclipse.org/mylyn/bugs/</a>
Steffen
</pre>
</blockquote>
</body>
</html>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03428 seconds
] 
Search
Help
Register
Login
Home
