Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Mylyn » Local task commit message after updating to Mylyn 3.0.2
Local task commit message after updating to Mylyn 3.0.2 [message #58722] Tue, 30 September 2008 04:41 Go to next message
Eclipse User
Originally posted by: mauro.molinari.cardinis.com

Hello!
After updating to Mylyn 3.0.2 (from 3.0.1, using update manager), I have
a problem with the commit message automatically generated by Mylyn for
my working set.

Instead of:
task 47: Supporto a NPW per Personal Planner

now Mylyn suggests:
taskSupporto a NPW per Personal Planner

Please note that "Supporto a NPW per Personal Planner" is the name of my
local task and that the commit template is set to:

${connector.task.prefix} ${task.key}: ${task.description}
${task.url}

I don't know if the problem was introduced by 3.0.2 or 3.0.1, but I'm
sure it worked well with Mylyn 3.0.0 (and 2.x).

Is anyone having the same problem?

Mauro.
Re: Local task commit message after updating to Mylyn 3.0.2 [message #59066 is a reply to message #58722] Wed, 01 October 2008 18:42 Go to previous messageGo to next message
Steffen Pingel is currently offline Steffen Pingel
Messages: 706
Registered: July 2009
Senior Member
Hi Mauro,

the change you are describing is caused by an intentional fix that was made
for Mylyn 3.0.2:

242310: TaskKey CommitTemplateVariable should not use the task id
https://bugs.eclipse.org/bugs/show_bug.cgi?id=242310

The task id for local tasks is not displayed anywhere in the UI and
therefore should not be used as part of the default commit template.

If you replace ${task.key} by ${task.id} in the template you should be able
to get the id back for local tasks.

Steffen


> Hello!
> After updating to Mylyn 3.0.2 (from 3.0.1, using update manager), I have
> a problem with the commit message automatically generated by Mylyn for
> my working set.
>
> Instead of:
> task 47: Supporto a NPW per Personal Planner
>
> now Mylyn suggests:
> taskSupporto a NPW per Personal Planner
>
> Please note that "Supporto a NPW per Personal Planner" is the name of my
> local task and that the commit template is set to:
>
> ${connector.task.prefix} ${task.key}: ${task.description}
> ${task.url}
>
> I don't know if the problem was introduced by 3.0.2 or 3.0.1, but I'm
> sure it worked well with Mylyn 3.0.0 (and 2.x).
>
> Is anyone having the same problem?
>
> Mauro.
Re: Local task commit message after updating to Mylyn 3.0.2 [message #59166 is a reply to message #59066] Thu, 02 October 2008 04:26 Go to previous messageGo to next message
Eclipse User
Originally posted by: mauro.molinari.cardinis.com

Steffen Pingel ha scritto:
> Hi Mauro,
>
> the change you are describing is caused by an intentional fix that was made
> for Mylyn 3.0.2:
>
> 242310: TaskKey CommitTemplateVariable should not use the task id
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=242310
>
> The task id for local tasks is not displayed anywhere in the UI and
> therefore should not be used as part of the default commit template.
>
> If you replace ${task.key} by ${task.id} in the template you should be able
> to get the id back for local tasks.
>
> Steffen

Hi Steffen, thanks for your info.

However I have a few questions:

- if I change ${task.key} with ${task.id} is there any side effect for
Bugzilla tasks? Do I have to switch the template every time I switch
from the local repository to the Bugzilla repository?

- if ${task.key} does not work anymore for local tasks, I would expect
to see my commit message as:

task : Supporto a NPW per Personal Planner

because the commit template is:

${connector.task.prefix} ${task.key}: ${task.description}
${task.url}

Instead, it seems that Mylyn cuts " : ": why?

- what is now the default commit template in 3.0.2? I think this is
quite a "breaking change" to be included in 3.0.2 from 3.0.1... isn't
it? Apart from the fact that this totally breaks the link between CVS
history entries and local tasks (if it has ever worked... see my bug
#198361)...

Mauro.
Re: Local task commit message after updating to Mylyn 3.0.2 [message #59267 is a reply to message #59166] Thu, 02 October 2008 14:24 Go to previous messageGo to next message
Steffen Pingel is currently offline Steffen Pingel
Messages: 706
Registered: July 2009
Senior Member
> - if I change ${task.key} with ${task.id} is there any side effect for
> Bugzilla tasks? Do I have to switch the template every time I switch
> from the local repository to the Bugzilla repository?

Yes, this will also affect Bugzilla but since the key and id are equal for
Bugzilla it should have the same result.

Note that uou can define commit templates on a per project bases in the
project properties.

> - if ${task.key} does not work anymore for local tasks, I would expect
> to see my commit message as:
>
> task : Supporto a NPW per Personal Planner
>
> because the commit template is:
>
> ${connector.task.prefix} ${task.key}: ${task.description}
> ${task.url}
>
> Instead, it seems that Mylyn cuts " : ": why?

That could be be a bug.

> - what is now the default commit template in 3.0.2? I think this is
> quite a "breaking change" to be included in 3.0.2 from 3.0.1... isn't
> it? Apart from the fact that this totally breaks the link between CVS
> history entries and local tasks (if it has ever worked... see my bug
> #198361)...

The default commit template is still the same as in previous versions.

I understand that the change how task ids are handled for local tasks can
appear as an unexpected change in a minor release. The task id is internal
to some repositories such as the local repository or JIRA. Some
repositories even use long random generated text for task ids which looks
very odd if exposed in the UI. Therefore it was considered a bug that the
${task.key} template returned these ids which can still be explicitly
configured by using ${task.id}.

Steffen
Re: Local task commit message after updating to Mylyn 3.0.2 [message #59389 is a reply to message #59267] Fri, 03 October 2008 04:08 Go to previous message
Eclipse User
Originally posted by: mauro.molinari.cardinis.com

Steffen Pingel ha scritto:
> Yes, this will also affect Bugzilla but since the key and id are equal for
> Bugzilla it should have the same result.

Ok, thank you!

> Note that uou can define commit templates on a per project bases in the
> project properties.

But this does not help very much: I'm working on a project on which I
need to close some bugs (=> from Bugzilla repository) and develop some
functions that are not in bugzilla (=> I'm using local tasks). So, the
base is not the project. This is because we're not using just Bugzilla
to track our issues and local tasks are often handful to create change
sets for some group of changes.

Moreover, I'm not working with a single project, but with many projects
with dependencies to each other. So I think a project-specific commit
template is quite useless in my case.

>> - if ${task.key} does not work anymore for local tasks, I would expect
>> to see my commit message as:
>>
>> task : Supporto a NPW per Personal Planner
>>
>> because the commit template is:
>>
>> ${connector.task.prefix} ${task.key}: ${task.description}
>> ${task.url}
>>
>> Instead, it seems that Mylyn cuts " : ": why?
>
> That could be be a bug.

I opened bug #249572.

Thank you!
Mauro.
Re: Local task commit message after updating to Mylyn 3.0.2 [message #593798 is a reply to message #58722] Wed, 01 October 2008 18:42 Go to previous message
Steffen Pingel is currently offline Steffen Pingel
Messages: 706
Registered: July 2009
Senior Member
Hi Mauro,

the change you are describing is caused by an intentional fix that was made
for Mylyn 3.0.2:

242310: TaskKey CommitTemplateVariable should not use the task id
https://bugs.eclipse.org/bugs/show_bug.cgi?id=242310

The task id for local tasks is not displayed anywhere in the UI and
therefore should not be used as part of the default commit template.

If you replace ${task.key} by ${task.id} in the template you should be able
to get the id back for local tasks.

Steffen


> Hello!
> After updating to Mylyn 3.0.2 (from 3.0.1, using update manager), I have
> a problem with the commit message automatically generated by Mylyn for
> my working set.
>
> Instead of:
> task 47: Supporto a NPW per Personal Planner
>
> now Mylyn suggests:
> taskSupporto a NPW per Personal Planner
>
> Please note that "Supporto a NPW per Personal Planner" is the name of my
> local task and that the commit template is set to:
>
> ${connector.task.prefix} ${task.key}: ${task.description}
> ${task.url}
>
> I don't know if the problem was introduced by 3.0.2 or 3.0.1, but I'm
> sure it worked well with Mylyn 3.0.0 (and 2.x).
>
> Is anyone having the same problem?
>
> Mauro.
Re: Local task commit message after updating to Mylyn 3.0.2 [message #593845 is a reply to message #59066] Thu, 02 October 2008 04:26 Go to previous message
Mauro Molinari is currently offline Mauro Molinari
Messages: 277
Registered: July 2009
Senior Member
Steffen Pingel ha scritto:
> Hi Mauro,
>
> the change you are describing is caused by an intentional fix that was made
> for Mylyn 3.0.2:
>
> 242310: TaskKey CommitTemplateVariable should not use the task id
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=242310
>
> The task id for local tasks is not displayed anywhere in the UI and
> therefore should not be used as part of the default commit template.
>
> If you replace ${task.key} by ${task.id} in the template you should be able
> to get the id back for local tasks.
>
> Steffen

Hi Steffen, thanks for your info.

However I have a few questions:

- if I change ${task.key} with ${task.id} is there any side effect for
Bugzilla tasks? Do I have to switch the template every time I switch
from the local repository to the Bugzilla repository?

- if ${task.key} does not work anymore for local tasks, I would expect
to see my commit message as:

task : Supporto a NPW per Personal Planner

because the commit template is:

${connector.task.prefix} ${task.key}: ${task.description}
${task.url}

Instead, it seems that Mylyn cuts " : ": why?

- what is now the default commit template in 3.0.2? I think this is
quite a "breaking change" to be included in 3.0.2 from 3.0.1... isn't
it? Apart from the fact that this totally breaks the link between CVS
history entries and local tasks (if it has ever worked... see my bug
#198361)...

Mauro.
Re: Local task commit message after updating to Mylyn 3.0.2 [message #593880 is a reply to message #59166] Thu, 02 October 2008 14:24 Go to previous message
Steffen Pingel is currently offline Steffen Pingel
Messages: 706
Registered: July 2009
Senior Member
> - if I change ${task.key} with ${task.id} is there any side effect for
> Bugzilla tasks? Do I have to switch the template every time I switch
> from the local repository to the Bugzilla repository?

Yes, this will also affect Bugzilla but since the key and id are equal for
Bugzilla it should have the same result.

Note that uou can define commit templates on a per project bases in the
project properties.

> - if ${task.key} does not work anymore for local tasks, I would expect
> to see my commit message as:
>
> task : Supporto a NPW per Personal Planner
>
> because the commit template is:
>
> ${connector.task.prefix} ${task.key}: ${task.description}
> ${task.url}
>
> Instead, it seems that Mylyn cuts " : ": why?

That could be be a bug.

> - what is now the default commit template in 3.0.2? I think this is
> quite a "breaking change" to be included in 3.0.2 from 3.0.1... isn't
> it? Apart from the fact that this totally breaks the link between CVS
> history entries and local tasks (if it has ever worked... see my bug
> #198361)...

The default commit template is still the same as in previous versions.

I understand that the change how task ids are handled for local tasks can
appear as an unexpected change in a minor release. The task id is internal
to some repositories such as the local repository or JIRA. Some
repositories even use long random generated text for task ids which looks
very odd if exposed in the UI. Therefore it was considered a bug that the
${task.key} template returned these ids which can still be explicitly
configured by using ${task.id}.

Steffen
Re: Local task commit message after updating to Mylyn 3.0.2 [message #593929 is a reply to message #59267] Fri, 03 October 2008 04:08 Go to previous message
Mauro Molinari is currently offline Mauro Molinari
Messages: 277
Registered: July 2009
Senior Member
Steffen Pingel ha scritto:
> Yes, this will also affect Bugzilla but since the key and id are equal for
> Bugzilla it should have the same result.

Ok, thank you!

> Note that uou can define commit templates on a per project bases in the
> project properties.

But this does not help very much: I'm working on a project on which I
need to close some bugs (=> from Bugzilla repository) and develop some
functions that are not in bugzilla (=> I'm using local tasks). So, the
base is not the project. This is because we're not using just Bugzilla
to track our issues and local tasks are often handful to create change
sets for some group of changes.

Moreover, I'm not working with a single project, but with many projects
with dependencies to each other. So I think a project-specific commit
template is quite useless in my case.

>> - if ${task.key} does not work anymore for local tasks, I would expect
>> to see my commit message as:
>>
>> task : Supporto a NPW per Personal Planner
>>
>> because the commit template is:
>>
>> ${connector.task.prefix} ${task.key}: ${task.description}
>> ${task.url}
>>
>> Instead, it seems that Mylyn cuts " : ": why?
>
> That could be be a bug.

I opened bug #249572.

Thank you!
Mauro.
Previous Topic:Usability around the current task
Next Topic:Files lost from context
Goto Forum:
  


Current Time: Sat Apr 19 03:07:50 EDT 2014

Powered by FUDForum. Page generated in 0.05436 seconds