Bugzilla – Full Text Bug Listing
| Summary: | Environment Variables (or Similar) in Mylyn SCM Commit Messages | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Jamie Jackson <jamiejaxon> |
| Component: | Mylyn | Assignee: | Mylyn Inbox <mylyn-inbox> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |
My current project asks us to follow a certain format for our commit messages. (The project uses SVN.) In Mylyn format, it would translate to something like this: ${USER_INITIALS}: ${task.key} [(${connector.task.prefix}) "${task.description}"] - The ${USER_INITIALS} variable is "pseudo-code", while the rest are working Mylyn commit variables. It would be slick if I could use an environment variable, and then commit the .settings/org.eclipse.mylyn.team.ui.prefs into SCM. Then, everyone on the project could use it. I have tried the actual pseudo-code above (and also the already-existing PATH and USER environment variables). None of these resolves, apparently, because upon commit, they are replaced with an empty string. Is there a solution? P.S. Why not just rely on the SVN username, which is already a property of every SVN commit? Because we have integrated SVN with our LDAP server, and it returns our (numeric) EMPLID, which nobody could attribute without manual lookup. Therefore, it's not terribly useful for at-a-glance attribution (which is what is desired). Also, I'm not interested in SVN hooks, because I'm looking for a client-side solution (that's where it would be appropriate to have the variables set).