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
signature.asc
Description: Digital signature