Maven SCM

Ability to assign an issue tracking to add, lock, and checkin

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.0-alpha-1
  • Fix Version/s: future
  • Component/s: maven-scm-api
  • Labels:
    None
  • Environment:
    xp, maven 1.0.2
  • Number of attachments :
    0

Description

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

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dan Tran added a comment -

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.

Show
Dan Tran added a comment - 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.
Hide
Permalink
Trygve Laugstøl added a comment -

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.

Show
Trygve Laugstøl added a comment - 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.
Hide
Permalink
Dan Tran added a comment -

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?

Show
Dan Tran added a comment - 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?
Hide
Permalink
Dan Tran added a comment -

It also hits

ScmManager interface
maven-scm-plugin
TCK

Show
Dan Tran added a comment - It also hits ScmManager interface maven-scm-plugin TCK
Hide
Permalink
Emmanuel Venisse added a comment -

Dan Tran,

Do you want work on it?

Show
Emmanuel Venisse added a comment - Dan Tran, Do you want work on it?
Hide
Permalink
Jeff Jensen added a comment -

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.

Show
Jeff Jensen added a comment - 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.
Hide
Permalink
Dan Tran added a comment -

OK, i will look into it.

Show
Dan Tran added a comment - OK, i will look into it.
Emmanuel Venisse made changes -
Field Original Value New Value
Workflow jira [ 34629 ] Maven New [ 53281 ]
Emmanuel Venisse made changes -
Fix Version/s future [ 12423 ]
Hide
Permalink
JR added a comment -

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?

Show
JR added a comment - 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?
Hide
Permalink
ajbanck added a comment -

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

Show
ajbanck added a comment - 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

People

  • Assignee:
    Unassigned
    Reporter:
    Dan Tran
Vote (1)
Watch (1)

Dates

  • Created:
    Updated: