[ http://jira.codehaus.org/browse/SCM-38?page=comments#action_41657 ]
Dan Tran commented on SCM-38: ----------------------------- 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? > Ability to assign an issue tracking to add, lock, and checkin > ------------------------------------------------------------- > > Key: SCM-38 > URL: http://jira.codehaus.org/browse/SCM-38 > Project: Maven SCM > Type: New Feature > Components: maven-scm-api > Versions: 1.0-alpha-1 > Environment: xp, maven 1.0.2 > Reporter: Dan Tran > > > Clearcase and starteam (if configured) insist to have an associate issue > id ( ie activity in clearcase, CR/activity/task in starteam) during lock, > add, and checkin commands. > Suggest to add "issue" argument for those commands in maven-scm-api interface -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
