You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scm-dev@maven.apache.org by "Dan Tran (JIRA)" <ji...@codehaus.org> on 2005/06/02 08:46:21 UTC
[jira] Created: (SCM-38) Ability to assign an issue tracking to add, lock, and checkin
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
Re: SCM API was: [jira] Commented: (SCM-38) Ability to assign an issue tracking to add, lock, and checkin
Posted by Trygve Laugstøl <tr...@student.matnat.uio.no>.
On Sat, Jun 11, 2005 at 11:37:44PM -0700, dan tran wrote:
> So far I know CVS/SVN/StartTeam work well the current maven-scm-api interface.
> What else we have lelf?
>
> MKS, Perforce, PVCS, ClearCase
>
> It would be nice to understand what obstacles the other providers are
> facing before
> we try to overhaul the interface.
>
> For Clearcase I think it is quite impossible to implement and satisfy
> everyone requirements. Clearcase has so of many options and practices
> that we may end up to have few Clearcase providers. For example,
> Luntbuid currently has
> 2 Clearcase providers (clearcase base, and clearcase UCM) those not even
> satisfy my clearcase practice. I am planning to implement a Clearcase provider
> that will be specific to my current practice ( and hope some one
> with the same practice can reuse it)
All the SCM Commands take a Map context that they're executing in so I'm
hoping that we can enable per scm provider configuration in a better way
that we're doing today. This should make it possible to have a single
ClearCase provider while we make this provider more flexible and
configurable based on user configuration.
> Question: what is the scope of maven-scm-api? a full SCM implementation or
> just enough for build automation? I favor the later since It is quite
> possible that
> the current maven-scm-api can be implemented by all providers, of course there
> will be some twist here and there (like my case, asking for an 'issue' )
I would say as much as possible, using these libraries to create something
like viewcvs is also something that I've been thinking of.
--
Trygve
Re: SCM API was: [jira] Commented: (SCM-38) Ability to assign an issue tracking to add, lock, and checkin
Posted by dan tran <da...@gmail.com>.
So far I know CVS/SVN/StartTeam work well the current maven-scm-api interface.
What else we have lelf?
MKS, Perforce, PVCS, ClearCase
It would be nice to understand what obstacles the other providers are
facing before
we try to overhaul the interface.
For Clearcase I think it is quite impossible to implement and satisfy
everyone requirements. Clearcase has so of many options and practices
that we may end up to have few Clearcase providers. For example,
Luntbuid currently has
2 Clearcase providers (clearcase base, and clearcase UCM) those not even
satisfy my clearcase practice. I am planning to implement a Clearcase provider
that will be specific to my current practice ( and hope some one
with the same practice can reuse it)
Question: what is the scope of maven-scm-api? a full SCM implementation or
just enough for build automation? I favor the later since It is quite
possible that
the current maven-scm-api can be implemented by all providers, of course there
will be some twist here and there (like my case, asking for an 'issue' )
-Dan
On 6/11/05, Jason van Zyl <ja...@maven.org> wrote:
> On Sun, 2005-06-12 at 14:25 +1000, Brett Porter wrote:
> > Is it possible we could give the API a once over before we try to grow it?
> >
> > Mike Esler previously talked about changing the API to be more use case
> > driven:
> > http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200505.mbox/%3c42836076.5050801@apache.org%3e
> > http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200505.mbox/%3c1116024858.22204.234103150@webmail.messagingengine.com%3e
> > (read the threads, in particular Jason's reply to the latter about
> > dropping the Manager)
> >
> > I think we could fairly quickly come up with a set of ideal interfaces,
> > then start talking about how to add things like this. We don't need to
> > do a big change to the API immediately, but start pushing it in the
> > direction of the final design.
> >
> > Thoughts?
>
> One thing for sure is the provider interface needs to have the methods
> that the manager has right now and the manager can be pushed off to
> another build.
>
> Reforming the API with folks now on the list with experience outside our
> predominantly CVS/SVN view would definitely be good along with the
> suggestion of Mike.
>
> > - Brett
> >
> > Dan Tran (JIRA) wrote:
> >
> > > [ http://jira.codehaus.org/browse/SCM-38?page=comments#action_41084 ]
> > >
> > >Dan Tran commented on SCM-38:
> > >-----------------------------
> > >
> > >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.
> > >
> > >
> > >
> > >
> > >
> > >
> > >>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
> > >>
> > >>
> > >
> > >
> > >
> >
> >
> --
> jvz.
>
> Jason van Zyl
> jason at maven.org
> http://maven.apache.org
>
> believe nothing, no matter where you read it,
> or who has said it,
> not even if i have said it,
> unless it agrees with your own reason
> and your own common sense.
>
> -- Buddha
>
>
Re: SCM API was: [jira] Commented: (SCM-38) Ability to assign an
issue tracking to add, lock, and checkin
Posted by Jason van Zyl <ja...@maven.org>.
On Sun, 2005-06-12 at 14:25 +1000, Brett Porter wrote:
> Is it possible we could give the API a once over before we try to grow it?
>
> Mike Esler previously talked about changing the API to be more use case
> driven:
> http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200505.mbox/%3c42836076.5050801@apache.org%3e
> http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200505.mbox/%3c1116024858.22204.234103150@webmail.messagingengine.com%3e
> (read the threads, in particular Jason's reply to the latter about
> dropping the Manager)
>
> I think we could fairly quickly come up with a set of ideal interfaces,
> then start talking about how to add things like this. We don't need to
> do a big change to the API immediately, but start pushing it in the
> direction of the final design.
>
> Thoughts?
One thing for sure is the provider interface needs to have the methods
that the manager has right now and the manager can be pushed off to
another build.
Reforming the API with folks now on the list with experience outside our
predominantly CVS/SVN view would definitely be good along with the
suggestion of Mike.
> - Brett
>
> Dan Tran (JIRA) wrote:
>
> > [ http://jira.codehaus.org/browse/SCM-38?page=comments#action_41084 ]
> >
> >Dan Tran commented on SCM-38:
> >-----------------------------
> >
> >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.
> >
> >
> >
> >
> >
> >
> >>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
> >>
> >>
> >
> >
> >
>
>
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
believe nothing, no matter where you read it,
or who has said it,
not even if i have said it,
unless it agrees with your own reason
and your own common sense.
-- Buddha
Re: SCM API was: [jira] Commented: (SCM-38) Ability to assign an
issue tracking to add, lock, and checkin
Posted by Brett Porter <br...@apache.org>.
Is it possible we could give the API a once over before we try to grow it?
Mike Esler previously talked about changing the API to be more use case
driven:
http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200505.mbox/%3c42836076.5050801@apache.org%3e
http://mail-archives.apache.org/mod_mbox/maven-scm-dev/200505.mbox/%3c1116024858.22204.234103150@webmail.messagingengine.com%3e
(read the threads, in particular Jason's reply to the latter about
dropping the Manager)
I think we could fairly quickly come up with a set of ideal interfaces,
then start talking about how to add things like this. We don't need to
do a big change to the API immediately, but start pushing it in the
direction of the final design.
Thoughts?
- Brett
Dan Tran (JIRA) wrote:
> [ http://jira.codehaus.org/browse/SCM-38?page=comments#action_41084 ]
>
>Dan Tran commented on SCM-38:
>-----------------------------
>
>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.
>
>
>
>
>
>
>>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
>>
>>
>
>
>
[jira] Commented: (SCM-38) Ability to assign an issue tracking to add, lock, and checkin
Posted by "Dan Tran (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-38?page=comments#action_41084 ]
Dan Tran commented on SCM-38:
-----------------------------
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.
> 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
[jira] Commented: (SCM-38) Ability to assign an issue tracking to add, lock, and checkin
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-38?page=comments#action_41092 ]
Trygve Laugstol commented on SCM-38:
------------------------------------
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.
> 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
[jira] Commented: (SCM-38) Ability to assign an issue tracking to add, lock, and checkin
Posted by "Dan Tran (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (SCM-38) Ability to assign an issue tracking to
add, lock, and checkin
Posted by "Dan Tran (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-38?page=comments#action_57711 ]
Dan Tran commented on SCM-38:
-----------------------------
OK, i will look into it.
> 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
[jira] Commented: (SCM-38) Ability to assign an issue tracking to add, lock, and checkin
Posted by "Dan Tran (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-38?page=comments#action_41660 ]
Dan Tran commented on SCM-38:
-----------------------------
It also hits
ScmManager interface
maven-scm-plugin
TCK
> 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
[jira] Commented: (SCM-38) Ability to assign an issue tracking to
add, lock, and checkin
Posted by "Jeff Jensen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-38?page=comments#action_57710 ]
Jeff Jensen commented on SCM-38:
--------------------------------
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.
> 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
[jira] Commented: (SCM-38) Ability to assign an issue tracking to
add, lock, and checkin
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-38?page=comments#action_57650 ]
Emmanuel Venisse commented on SCM-38:
-------------------------------------
Dan Tran,
Do you want work on it?
> 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