Kindly send me some getting started info about plugin development, never developed a plugin ealier. My approach would be to do it as fast as possible.
-----Original Message-----
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 05, 2006 2:35 PM
To: scm-dev@maven.apache.org
Subject: Re: The best approach to extend ScmProvider
If you know well scm commands, a new scm provider can be implemented in 2-3 days.
The minimal commands are add, checkin, checkout, changelog, remove, tag, update, status, and the TCK
implementation for validation of code.
Emmanuel
[EMAIL PROTECTED] a écrit :
>
>
>
>
>
> A task and a change set is almost the same thing.
>
> I also have plans to implement support for CM Synergy. However, as my
> workload is pretty heavy at the moment, I will not be able to start
> this until a couple of weeks from now.
>
> Does anyone knows approximately how long it takes to implement support
> for a new SCM provider?
>
> If you start please let me know. I'll be happy to test your work if
> you implement something.
>
> Regards
>
> Henrik
>
>
>
>
>
>
>
>
> "Zsolt" <[EMAIL PROTECTED]>
> 2006-04-05 07:24
>
> Please respond to
> scm-dev@maven.apache.org
>
>
> To
> <scm-dev@maven.apache.org>
> cc
>
> Subject
> RE: The best approach to extend ScmProvider
>
>
>
>
>
>
> I'm not sure what you exactly mean. CM-Synergy task is created BEFORE
> you checkout.
>
> Zsolt
>
>
>>-----Original Message-----
>>From: Torbjorn Smorgrav [mailto:[EMAIL PROTECTED]]
>>Sent: Tuesday, April 04, 2006 4:41 PM
>>To: scm-dev@maven.apache.org
>>Subject: RE: The best approach to extend ScmProvider
>>
>>Is it the same as a change set?
>>A change set you can append to?
>>
>>Torbjorn
>>
>>
>>
>>-----Original Message-----
>>From: Zsolt [mailto:[EMAIL PROTECTED]]
>>Sent: 4. april 2006 16:00
>>To: scm-dev@maven.apache.org
>>Subject: RE: The best approach to extend ScmProvider
>>
>>
>>In Cm-Synergy (ClearCase has that also) you can checkin with a task
>
> created
>
>>and maintained by CM-Synergy, and I would like to browse the tasks
>
> created
>
>>in CM-Synergy.
>>
>>Zsolt
>>
>>
>>>-----Original Message-----
>>>From: Torbjorn Smorgrav
>>>[mailto:[EMAIL PROTECTED]]
>>>Sent: Tuesday, April 04, 2006 9:31 AM
>>>To: scm-dev@maven.apache.org
>>>Subject: RE: The best approach to extend ScmProvider
>>>
>>>What is a task in this context?
>>>
>>>Torbjorn
>>>
>>>-----Original Message-----
>>>From: Zsolt [mailto:[EMAIL PROTECTED]]
>>>Sent: 3. april 2006 19:31
>>>To: scm-dev@maven.apache.org
>>>Subject: RE: The best approach to extend ScmProvider
>>>
>>>
>>>Thank you Carlos,
>>>
>>>I will also need a merthod: listTasks (or something like that) that
>>
>>returns
>>
>>>the tasks of the version control system.
>>>
>>>Can (should) I use commit to the repository?
>>>
>>>Zsolt
>>>
>>>
>>>>-----Original Message-----
>>>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
>
> Carlos
>
>>>>Sanchez
>>>>Sent: Monday, April 03, 2006 6:26 PM
>>>>To: scm-dev@maven.apache.org
>>>>Subject: Re: The best approach to extend ScmProvider
>>>>
>>>>I'd create a new list method. Providers that don't support a list
>>>>operation can explain in the javadocs that they don't support it or
>>>>that the operation is not efficient because it requires checkout.
>>>>
>>>>On 4/1/06, Zsolt <[EMAIL PROTECTED]> wrote:
>>>>
>>>>>From the source code:
>>>>>
>>>>> public interface ScmProvider
>>>>>
>>>>>
>>>>>I'm very under time pressure:
>>>>>
>>>>>We have our own (limited scm support) and have to decide until
>>>>>Monday whether we join to scm-maven (of course we would make all
>
> modifications
>
>>>>>available) or extend our scm implementation.
>>>>>
>>>>>For us it is a must that we can get the list of files of a
>>>>>directory directly from the repository and we must also support
>>>>>huge projects
>>>
>>>(thus
>>>
>>>>an
>>>>
>>>>>entire checkout is not an option).
>>>>>
>>>>>"svn list -v" does exactly what we need. For CVS we could execute:
>>>>> cvs checkout -l .... DIRECTORY
>>>>>into a temporary directory read the contents of CVS/* files (to get
>>>>>revision, modification date etc.) and remove the temporary
>>>>>directors.
>>>>>
>>>>>I don't know ClearCase but I guess it has also a list command.
>>>>>
>>>>>If we join to scm-maven we will very probably implement CM-Synergy
>>>>
>>>>because
>>>>
>>>>>one of our customers uses only Cm-Synergy it.
>>>>>
>>>>>Please give me hints as soon as possible.
>>>>>
>>>>>Zsolt
>>>>>
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
>>>
>>>Carlos
>>>
>>>>>>Sanchez
>>>>>>Sent: Saturday, April 01, 2006 10:24 AM
>>>>>>To: scm-dev@maven.apache.org
>>>>>>Subject: Re: The best approach to extend ScmProvider
>>>>>>
>>>>>>Not sure if ScmProvider is an interface but if it is we better add
>
> the
>
>>>>>>method to it before 1.0 and implement in the providers throwing a
>
> not
>
>>>>>>implemented exception, because if not we'll need to create another
>>>>>>interface to avoid breaking backwards compatibility in 1.x
>>>>>>
>>>>>>On 4/1/06, Zsolt <[EMAIL PROTECTED]> wrote:
>>>>>>
>>>>>>>Hi,
>>>>>>>
>>>>>>>I need to extend ScmProvider to support a list method (like svn
>>>
>>>list).
>>>
>>>>>>What
>>>>>>
>>>>>>>is the best approach to do that?
>>>>>>>
>>>>>>>I need this functionally for CVS, svn and clearcase. Later we
>
> might
>
>>>>even
>>>>
>>>>>>add
>>>>>>
>>>>>>>CM Synergy support for maven scm.
>>>>>>>
>>>>>>>What is the best approach?
>>>>>>>
>>>>>>>Should I use the maven repository or create my own one?
>>>>>>>
>>>>>>>I work with eclipse. How should I setup the project compile
>>>>
>>>>everything?
>>>>
>>>>>>>Zsolt
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>--
>>>>>>I could give you my word as a Spaniard.
>>>>>>No good. I've known too many Spaniards.
>>>>>> -- The Princess Bride
>>>>>
>>>>>
>>>>
>>>>--
>>>>I could give you my word as a Spaniard.
>>>>No good. I've known too many Spaniards.
>>>> -- The Princess Bride
>
>
>
>
>
>
> ______________________________________________________________________
> _________________________________________
>
>
> This e-mail communication (and any attachment/s) may contain
> confidential or privileged information and is intended only for the
> individual(s) or entity named above and to others who have been
> specifically authorized to receive it. If you are not the intended
> recipient, please do not read, copy, use or disclose the contents of
> this communication to others. Please notify the sender that you have
> received this e-mail in error by reply e-mail, and delete the e-mail
> subsequently. Thank you.
> ______________________________________________________________________
> ___________________________________________
>
>
>
> Ce message (ainsi que le(s) fichier/s), transmis par courriel, peut
> contenir des renseignements confidentiels ou protégés et est destiné à
> l?usage exclusif du destinataire ci-dessus. Toute autre personne est
> par les présentes avisée qu?il est strictement interdit de le
> diffuser, le distribuer ou le reproduire. Si vous l?avez reçu par
> inadvertance, veuillez nous en aviser et détruire ce message. Merci.
> _________________________________________________________________________________________________________________
>
>
>
>
> (See attached file: C.htm)
>
>
> ----------------------------------------------------------------------
> --
>
>
> A task and a change set is almost the same thing.
>
> I also have plans to implement support for CM Synergy. However, as my
> workload is pretty heavy at the moment, I will not be able to start this
> until a couple of weeks from now.
>
> Does anyone knows approximately how long it takes to implement support
> for a new SCM provider?
>
> If you start please let me know. I'll be happy to test your work if
> you
> implement something.
>
> Regards
>
> Henrik
>
>
>
>
>
>
>
> *"Zsolt" <[EMAIL PROTECTED]>*
> 2006-04-05 07:24
> Please respond to
> scm-dev@maven.apache.org
>
>
>
> To
> <scm-dev@maven.apache.org>
> cc
>
> Subject
> RE: The best approach to extend ScmProvider
>
>
>
>
>
>
>
>
> I'm not sure what you exactly mean. CM-Synergy task is created BEFORE
> you checkout.
>
> Zsolt
>
> >-----Original Message-----
> >From: Torbjorn Smorgrav
> [mailto:[EMAIL PROTECTED]]
> >Sent: Tuesday, April 04, 2006 4:41 PM
> >To: scm-dev@maven.apache.org
> >Subject: RE: The best approach to extend ScmProvider
> >
> >Is it the same as a change set?
> >A change set you can append to?
> >
> >Torbjorn
> >
> >
> >
> >-----Original Message-----
> >From: Zsolt [mailto:[EMAIL PROTECTED]]
> >Sent: 4. april 2006 16:00
> >To: scm-dev@maven.apache.org
> >Subject: RE: The best approach to extend ScmProvider
> >
> >
> >In Cm-Synergy (ClearCase has that also) you can checkin with a task
> created
> >and maintained by CM-Synergy, and I would like to browse the tasks created
> >in CM-Synergy.
> >
> >Zsolt
> >
> >>-----Original Message-----
> >>From: Torbjorn Smorgrav [mailto:[EMAIL PROTECTED]]
> >>Sent: Tuesday, April 04, 2006 9:31 AM
> >>To: scm-dev@maven.apache.org
> >>Subject: RE: The best approach to extend ScmProvider
> >>
> >>What is a task in this context?
> >>
> >>Torbjorn
> >>
> >>-----Original Message-----
> >>From: Zsolt [mailto:[EMAIL PROTECTED]]
> >>Sent: 3. april 2006 19:31
> >>To: scm-dev@maven.apache.org
> >>Subject: RE: The best approach to extend ScmProvider
> >>
> >>
> >>Thank you Carlos,
> >>
> >>I will also need a merthod: listTasks (or something like that) that
> >returns
> >>the tasks of the version control system.
> >>
> >>Can (should) I use commit to the repository?
> >>
> >>Zsolt
> >>
> >>>-----Original Message-----
> >>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Carlos
> >>>Sanchez
> >>>Sent: Monday, April 03, 2006 6:26 PM
> >>>To: scm-dev@maven.apache.org
> >>>Subject: Re: The best approach to extend ScmProvider
> >>>
> >>>I'd create a new list method. Providers that don't support a list
> >>>operation can explain in the javadocs that they don't support it or
> >>>that the operation is not efficient because it requires checkout.
> >>>
> >>>On 4/1/06, Zsolt <[EMAIL PROTECTED]> wrote:
> >>>> From the source code:
> >>>>
> >>>> public interface ScmProvider
> >>>>
> >>>>
> >>>> I'm very under time pressure:
> >>>>
> >>>> We have our own (limited scm support) and have to decide until Monday
> >>>> whether we join to scm-maven (of course we would make all
> modifications
> >>>> available) or extend our scm implementation.
> >>>>
> >>>> For us it is a must that we can get the list of files of a directory
> >>>> directly from the repository and we must also support huge projects
> >>(thus
> >>>an
> >>>> entire checkout is not an option).
> >>>>
> >>>> "svn list -v" does exactly what we need. For CVS we could execute:
> >>>> cvs checkout -l .... DIRECTORY
> >>>> into a temporary directory read the contents of CVS/* files (to get
> >>>> revision, modification date etc.) and remove the temporary directors.
> >>>>
> >>>> I don't know ClearCase but I guess it has also a list command.
> >>>>
> >>>> If we join to scm-maven we will very probably implement CM-Synergy
> >>>because
> >>>> one of our customers uses only Cm-Synergy it.
> >>>>
> >>>> Please give me hints as soon as possible.
> >>>>
> >>>> Zsolt
> >>>>
> >>>> >-----Original Message-----
> >>>> >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
> >>Carlos
> >>>> >Sanchez
> >>>> >Sent: Saturday, April 01, 2006 10:24 AM
> >>>> >To: scm-dev@maven.apache.org
> >>>> >Subject: Re: The best approach to extend ScmProvider
> >>>> >
> >>>> >Not sure if ScmProvider is an interface but if it is we better
> add the
> >>>> >method to it before 1.0 and implement in the providers throwing a not
> >>>> >implemented exception, because if not we'll need to create another
> >>>> >interface to avoid breaking backwards compatibility in 1.x
> >>>> >
> >>>> >On 4/1/06, Zsolt <[EMAIL PROTECTED]> wrote:
> >>>> >> Hi,
> >>>> >>
> >>>> >> I need to extend ScmProvider to support a list method (like svn
> >>list).
> >>>> >What
> >>>> >> is the best approach to do that?
> >>>> >>
> >>>> >> I need this functionally for CVS, svn and clearcase. Later we might
> >>>even
> >>>> >add
> >>>> >> CM Synergy support for maven scm.
> >>>> >>
> >>>> >> What is the best approach?
> >>>> >>
> >>>> >> Should I use the maven repository or create my own one?
> >>>> >>
> >>>> >> I work with eclipse. How should I setup the project compile
> >>>everything?
> >>>> >>
> >>>> >> Zsolt
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >
> >>>> >
> >>>> >--
> >>>> >I could give you my word as a Spaniard.
> >>>> >No good. I've known too many Spaniards.
> >>>> > -- The Princess Bride
> >>>>
> >>>>
> >>>
> >>>
> >>>--
> >>>I could give you my word as a Spaniard.
> >>>No good. I've known too many Spaniards.
> >>> -- The Princess Bride
>
>
>
>
>
> ______________________________________________________________________
> _________________________________________
>
> This e-mail communication (and any attachment/s) may contain
> confidential or privileged information and is intended only for the
> individual(s) or entity named above and to others who have been
> specifically authorized to receive it. If you are not the intended
> recipient, please do not read, copy, use or disclose the contents of
> this communication to others. Please notify the sender that you have
> received this e-mail in error by reply e-mail, and delete the e-mail
> subsequently.
> Thank you.
> _________________________________________________________________________________________________________________
>
>
> Ce message (ainsi que le(s) fichier/s), transmis par courriel, peut
> contenir des renseignements confidentiels ou protégés et est destiné à
> l'usage exclusif du destinataire ci-dessus. Toute autre personne est par
> les présentes avisée qu'il est strictement interdit de le diffuser, le
> distribuer ou le reproduire. Si vous l'avez reçu par inadvertance,
> veuillez nous en aviser et détruire ce message.
> Merci.
> _________________________________________________________________________________________________________________
>
>
- - - - - - - 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 liablility for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
