[#SCM-117] Add parameters to scm configuration element

Maven SCM

Add parameters to scm configuration element

Created: 15/Dec/05 02:48 PM Updated: 13/Mar/07 08:28 AM

Component/s:

maven-scm-provider-starteam

Affects Version/s:

1.0-beta-2

Fix Version/s:

future

Time Tracking:

Not Specified

Issue Links:

Related

This issue relates to:

SCM-142 Starteam tree stale

Complexity:

Intermediate

Description

« Hide

It would be very nice to have the ability to add parameters to the scm element. For instance to add parameter to always force checkout. for instance in Starteam I would like to add -o so every time stcmd is called the parameters will be concatenated to the command line

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Dan Tran added a comment - 23/Jan/06 09:34 PM

What happen to your case is:

Developer remove the file
Decide to put it back
Comtinuum issues scm:update and fails due to unknow file status

[ Permlink | « Hide ]

Antonio D'Errico added a comment - 04/May/06 08:08 AM

Hi,
also for me a better flexibility in scm plugin configuration can be achieved using parameters to add to command line. For example I've a project configured under StarTeam that always ask the active item when I do a checkin, so the only way to perform such action is add the -active argument to command line.

[ Permlink | « Hide ]

Dan Tran added a comment - 09/May/06 11:30 AM

maven-scm-provider-starteam has a hidden system property that allow you to issue "-cr path" during checking

1. Create a CR using your starteam

2. pass -Dmaven.scm.issue=path to your CR

Would this work?

[ Permlink | « Hide ]

Giovanni Pedone added a comment - 21/Dec/06 11:11 AM

I honestly do not undertand and get the point of the previous comment.

The functionality to add command line parameters for the stcmd checkout command would be useful.
It gets executed with the -merge option, I think this has been done to save bandwidth since the force checkout option -o, would checkout ANY file even those which are current.
But I think that -merge option is not safe. Continuum should not have the "ability" to merge files.

thank you

[ Permlink | « Hide ]

Dan Tran added a comment - 21/Dec/06 12:11 PM

the merge param is used during "scm's update" only, not during the first checkout. Also according to me experience the merge is required in order to get the update to work when there are file changes in starteam server. You can help by taking out the merge and replace the jar with the one
in your continuum to see if it still works

[ Permlink | « Hide ]

Giovanni Pedone added a comment - 23/Dec/06 12:22 PM

The merge param is used also on the first checkout. Anyway, this doesnt matter that much, since when you first checkout a project, the working folder is empty

The issue arises when you do subsequent builds, then it is used the -merge option. This option means that if some file has changes on ST server and that same file has been changed in the local working directory, it will get merged automatically and without prompting.
Even though this situation would be not normal to happen, since no one should be supposed to go into Continuum working folder and modify any files, it is conceptually wrong to my opinion. As I said, Continuum should not be given the authority to merge files, since.conflicts may happen that may not be able to get automatically resolved.
Please tell me if all this is wrong.

[ Permlink | « Hide ]

Dan Tran added a comment - 23/Dec/06 01:21 PM

Are you sure the first checkout uses "merge" param? The checkout implementation does not use that

I also agree that continuum should not have authority to do the merge, please file a new JIRA. Feel free to fix the code and test it out

Thanks