[EMAIL PROTECTED] a écrit :

Hi and thanks for the info!

I'm new to both maven and maven-scm so bear with me...
I have checked out maven-scm from svn.

What would be the best solution to import this into Eclipse?

mvn eclipse:eclipse

Should I have each module (maven-scm-api, maven-scm-providers) as separate Eclipse projects?

yes, all eclipse projects will be generated by eclipse mojo

Eclipse has a different directory standard.

yes, with eclipse you can't add pom projects but only jar projects, so you'll 
need to remove them


I'm sorry if these are simple questions, but the documentation of doing this on the web site is quite thin.

http://maven.apache.org/plugins/maven-eclipse-plugin/overview.html
http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html

Emmanuel


Regards

Henrik







*"Torbjorn Smorgrav" <[EMAIL PROTECTED]>*
2006-03-22 21:54
Please respond to
scm-dev@maven.apache.org


        
To
        scm-dev@maven.apache.org
cc
        
Subject
        Re: Implementing support for CM Synergy?


        





Hi Henrik!

 > I posted this yesterday as well. But I haven't got any response yet. So
 > I'll ask again.
 > I want to implement support for CM Synergy.

I'll be happy to help you.
I recently added the Bazaar provider (yet to be released) so I can
at least guide you through the same path that I took.

 > What baseline should I use?

Use the current development baseline.
http://maven.apache.org/scm/source-repository.html

 > What do I need to check out?

Start with:

maven-scm-api/ <http://svn.apache.org/viewcvs.cgi/maven/scm/trunk/maven-scm-api/>
maven-scm-test/
<http://svn.apache.org/viewcvs.cgi/maven/scm/trunk/maven-scm-test/>

And a reference provider eg. maven-scm-provider-bazaar/
<http://svn.apache.org/viewcvs.cgi/maven/scm/trunk/maven-scm-providers/maven-scm-provider-bazaar/>
Perhapes choose one that is most similar to the CM Synergy

 > What class or interfaced do I need to implement?

What I did was change the implementation of an existing provider.
That way I got fast results and I learned the API one step at the time.

Basically what you need to implements is an (Abstract)ScmProvider and
its commands.

 > How can I test my provider?

1. Run unit tests from your IDE
The test classes in maven-scm-test was really helpfull to me. Try to
include a tck test
as soon as possible. See how the tck tests are implemented in the
reference provider (its a no brainer :).

It can be a bit tricky to setup your IDE to pickup your current
modifications and not the installed
version of the provider. Let me know it this becomes a problem.

2. Build and install the provider and test it with eg. "mvn
scm:checkout" on a project where
you have defined a scm url in the pom.xml.

This was probably a too short answer. But if you post your questions
as they come,
I'll do my best to help you. And in the end I like to make a mave-scm
howto webpage
with all of this.

Good luck,
Torbjørn
[attachment "C.htm" deleted by Henrik Jonsson/SE/Transport/Bombardier]




_______________________________________________________________________________________________________________ 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.
_________________________________________________________________________________________________________________


Reply via email to