Fine. I would test it. Yes, I have defined the scm url for MKS.
Regards.
-----Original Message-----
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 01, 2006 12:42 PM
To: scm-dev@maven.apache.org
Subject: Re: M2 : How to implement goals in SCM provider implementation ?
I guess you have define the scm url for MKS, right?
so, you can test it by adding this in your pom:
<scm>
<connection>scm:mks:mks_connection_parameters</connection>
<developerConnection>scm:mks:mks_connection_parameters</developerConnection>
</scm>
The first steap you can test is to add your provider as a dependency of maven-scm plugin and you'll
can try scm:checkout, scm:update and other.
If all is ok, you'll need to test it with changelog plugin, release plugin and Continuum.
For changelog and release plugins, you'll need to add your provider as a dependency in the plugin or
if you don't want to modify them for now, you can add it as a plugin dependency in your pom.
For continuum, put your provider in $CONTINUUM/apps/continuum/lib
Emmanuel
Sharma, Jaikumar a écrit :
> Hi Emmanuel,
> Initially, I have implemented the connect method other functionality
> in
> SCM provider for MKS plugin and it has been been built and installed in
> local repository. I want to know, how to configure this plugin in my pom
> so that I can test to connect to MKS provider, if it works or I have to
> change something ?
>
> Thanks for your help!
>
> Regards, Jaikumar
>
> -----Original Message-----
> From: Sharma, Jaikumar
> Sent: Monday, May 29, 2006 2:12 PM
> To: 'scm-dev@maven.apache.org'
> Subject: RE: M2 : How to implement goals in SCM provider
> implementation ?
>
>
> Thanks Emmanuel, that was the enlightment, I was expecting from you
> ;-)
>
> -----Original Message-----
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]]
> Sent: Monday, May 29, 2006 1:54 PM
> To: scm-dev@maven.apache.org
> Subject: Re: M2 : How to implement goals in SCM provider
> implementation ?
>
>
> ok, it what I thought :-)
>
> SCM providers don't know anythink about maven and goals. It's the role
> of scm plugin.
>
> SCM providers implements SCM commands and scm plugin use them with
> Maven-SCM APIs.
>
> Emmanuel
>
> Sharma, Jaikumar a écrit :
> > Emmanuel, As per the documentation on
> >
> http://maven.apache.org/guides/plugin/guide-java-plugin-development.ht
> > ml
> > . A simple Mojo needs to have a '@goal', well I mentioned 'goals' --
> > mentioned term in a general way. Please see below some snippet from the
> > above mentioned web link.
> >
> > Well, I think I have not hurt you ;-)
> >
> > Rgds, Jaikumar
> >
> > -----------------------------------------------------------------
> > package sample.plugin;
> >
> > import org.apache.maven.plugin.AbstractMojo;
> > import org.apache.maven.plugin.MojoExecutionException;
> >
> > /**
> > * @goal sayhi
> > * @description Says "Hi" to the user
> > */
> > public class GreetingMojo extends AbstractMojo
> > {
> > public void execute() throws MojoExecutionException
> > {
> > getLog().info("Hello, world.");
> > }
> > }
> >
> > -----------------------------------------------------------------
> >
> > -----Original Message-----
> > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, May 29, 2006 1:14 PM
> > To: scm-dev@maven.apache.org
> > Subject: Re: M2 : How to implement goals in SCM provider
> > implementation ?
> >
> >
> > what do you mean by goals?
> >
> > Emmanuel
> >
> > Sharma, Jaikumar a écrit :
> > > I am working on SCM provider implementation for MKS. Could somebody
> > > throw some lights on goals implementation for SCM provider. I had a
> > look > on SCM provider implementation for VSS, but could not find the
> > goals > definition in any of the classes ? >
> > > Thanks!
> > >
> > > Jaikumar
> >
>
> - - - - - - - DISCLAIMER- - - - - - - -
> Unless indicated otherwise, the information contained in this message
> is
> privileged and confidential, and is intended only for the use of the
> addressee(s) named above and others who have been specifically
> authorized to receive it. If you are not the intended recipient, you are
> hereby notified that any dissemination, distribution or copying of this
> message and/or attachments is strictly prohibited. The company accepts
> no liability for any damage caused by any virus transmitted by this
> email. Furthermore, the company does not warrant a proper and complete
> transmission of this information, nor does it accept liability for any
> delays. If you have received this message in error, please contact the
> sender and delete the message. Thank you.
>
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
