We're not talking about the scm api... of course that has a login ability. We're talking about the scm goals (maven-scm-plugin)
Eric On 7/7/06, dan tran <[EMAIL PROTECTED]> wrote:
maven-scm-api does haave login interface, however provider like svn, starteam, clearcase, etc does not have login action and therefor not implement that interface. That is why you dont see login action surfaces to maven-scm-plugin. About missing goal's doc, please file JIRA -D On 7/7/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote: > > Thanks Eric, I was not sure whether I should post this questions to > maven users list or developer list.Though, to me it looks, more > developer list question than user list. > > Is it not worthwhile to provide "login" as a seperate goal ? or there > are > > some good reasons to not to provide this ? > > What would be the value in a goal that logs in, but does not perform any > actions? > > I do not believe that logging in into a system / repository is not an > action, if this would have been like that then what is meaning of > security and why operating system providers (Microsoft , open source > Linux to name a few) implemented this behaviour into their system ? > > Thanks , Jaikumar > > > -----Original Message----- > From: Eric Redmond [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 08, 2006 2:39 AM > To: Maven Users List > Subject: Re: maven-scm-plugin goals question > > > Please do not cross-post between lists. More below. > > On 7/7/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote: > > > > Dear all, > > > > As I see at the following URL goals provided by maven-scm-plugin, > > these goals are general goals, but at the same time, certain actions > > > / operations which are specific to a particular SCM does not really > > match (for readibility / documentation reasons) to these goals. > > > > http://maven.apache.org/scm/plugins/plugin-info.html > > <http://maven.apache.org/scm/plugins/plugin-info.html> > > > > > > For instance, take the login action, which I think every provider > > implements for it repository, and in most of the cases with other > > providers which are implemented, login has been wrapped in URL in the > > pom and there itself login take place. > > > Is it not worthwhile to provide "login" as a seperate goal ? or there > are > > some good reasons to not to provide this ? > > > What would be the value in a goal that logs in, but does not perform any > actions? > > Next, I would appreciate, if somebody could point me to the purpose of > the > > following goals with repect to the provider repository : > > > > scm:diff > > scm:status > > scm:tag > > scm:unedit > > > If I do not implement any of the goals or only implement which are > relevent > > / common goals which are relevent to my provider , then at the higher > > level would I be missing any of the functinality provided by Maven ? > > > Of course, but that's not important. If an implementation does not > provide > for a particular goal, then it just will not be available. SCM is just > like > any other API. Sometimes an implementation of an API cannot provide all > required functionality. Naturally, it is best to try, but if your > provider > does not have "tag" for example, naturally that goal cannot be used > correctly. > > Regards, Jaikumar > > > > Thanks; > Eric > >
