I would like to go forward with this enhancement by adding
'issue' argument to add/checkin/lock command interfaces.

Please give some sort of blessing before I start the changes to
all provider implementations.

Note that, only StarTeam and (future) Clearcase would do something
with this 'issue', other providers ignore it.

I assume all providers can take some sort of message while commiting so we can just insert the issue id on the first line of the commit message.

trygve, we can not assume that message is the issue. I know for sure starteam can take both message and
issue. Denpending on system policy, issue can be optional or manditory (like mine)

I am also looking into the code to see the impact if I introduce one more param for a command. It will hit

DefaultScmManager
CommandParameter
The Command Interface

and

The command implementations of all providers.

Since the request to add "ISSUE" parameter only apply to StartTeam. is it kind a odd?

Is the a better solution?

Any blessing before I implement my proposed solution?

It also hits

ScmManager interface
maven-scm-plugin
TCK

Dan Tran,

Do you want work on it?

Note that Perforce also needs to use this. Many installations turn on a "require job" rule/trigger. A ClearCase activity is the same as a Perforce job. For Perforce, the issue must be a string, which is the job name. This is also different than the checkin message for Perforce.

OK, i will look into it.

Has this been looked into any further? I have a definite need for it with Perforce. Or is there a workaround somewhere in the scm or release plugins?

I see that scm-starteam has the "hidden features" - is there a starteam-only implementation then?

With Perforce often both a job and (specific) describtion are required.
For Perforce I created a patch that enables a system property to specify a job, for example -Dmaven.scm.jobs=JOB1234. Patch is attached to SCM-354, http://jira.codehaus.org/browse/SCM-354
As it looks like there is no generic solution soon, would be great if this can be solved for the providers

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.