Bug 151419 - [Wizards] Allow variables in commit comment templates
Summary: [Wizards] Allow variables in commit comment templates
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-07-21 11:51 EDT by Christopher Orr CLA
Modified: 2019-09-06 16:18 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Orr CLA 2006-07-21 11:51:44 EDT
I saw the nice new Comment Template feature for Team/CVS in 3.2 and thought, because there was a preview textarea, that it might allow me to insert some dynamic comments, e.g. {date}, {user}, {file_name} etc..

So yes, it would be nice if Comment Templates could accept variables much like Code Templates do.

Ideally, there could also be a way of editing the format in which each file in a changeset is displayed, e.g. for a commit with changed files x/Foo.java and y/Bar.java we could generate text like:

\t* x/Foo.java: 
\t* y/Bar.java:
Comment 1 Bogdan Gheorghe CLA 2006-07-31 15:35:20 EDT
This could be an interesting feature. Unfortunately, the platform doesn't have a centralized place to share variables - all of the code template code belongs to the JDT plugin. So to provide the requested functionality, we would need to put in some sort of variable definition page. There is a plugin that has been separated out for working with variables - org.eclipse.core.variables - which could be of help.

However, for 3.3, we, the CVS/Team team, simply don't have the manpower to tackle this enhancement request. As always,  if anyone is interested in contributing this feature, we would be more than happy to consider a patch and provide feedback. Thanks!
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:18:19 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.