Thank you for the replies, it was really helpful. However, when I tried
to run "checkout-project" goal in my directory, I received the following
errors, any suggestions on what I should do to fix the error? I received
the same error when I ran scm:perform-release.
C:\workground>maven scm:checkout-project -Dmaven.scm.method=cvs
-Dmaven.scm.cvs.
module=muCalcC
-Dmaven.scm.cvs.root=:pserver:[EMAIL PROTECTED]:/home/m
unicvs/muni_cvs -Dmaven.scm.checkout.dir=.
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.1
build:start:
scm:parse-connection:
[echo] Using connection:
scm:cvs:pserver:[EMAIL PROTECTED]:/home/m
unicvs/muni_cvs:muCalcC
Using SCM method: cvs
Using CVSROOT: :pserver:[EMAIL PROTECTED]:/home/municvs/muni_cvs
Using module: muCalcC
scm:validate:
scm:checkout-project:
scm:cvs-checkout-project:
[echo] Checking out muCalcC; from CVSROOT:
:pserver:[EMAIL PROTECTED]
com:/home/municvs/muni_cvs
[delete] Deleting directory C:\workground\target\checkouts\muCalcC
[mkdir] Created dir: C:\workground\target\checkouts\muCalcC
[cvs] Using cvs passfile: C:\Documents and Settings\xxxxxx\.cvspass
BUILD FAILED
File...... C:\Documents and
Settings\xxxxx\.maven\cache\maven-scm-plugin-1.4.1
\plugin.jelly
Element... ant:cvs
Line...... 245
Column.... 9
java.io.IOException: CreateProcess: cvs
-d:pserver:[EMAIL PROTECTED]:/
home/municvs/muni_cvs -q checkout -P muCalcC error=2
Total time: 3 seconds
Finished at: Wed Dec 22 10:17:04 EST 2004
Thank you,
-Wendy
----- Original Message Follows -----
> To bootstrap your project (i.e. the first checkout of a real project)
> , use :
>
> maven scm:checkout-project
> -Dmaven.scm.method=cvs
> -Dmaven.scm.cvs.module=project4
> -Dmaven.scm.cvs.root=:pserver:[EMAIL PROTECTED]:/home/cvspublic
> -Dmaven.scm.checkout.dir=.
>
> For this to really work with a secure password, you need to have a
> cvspass file. I discuss how to create a cvspass in my book (which you
> are clearly refering to) at www.milindparikh.com. The scm plugin does
> all the work. No more ant scripts to bootstrap the checkout process.
>
> Once you have the project.xml, then you make the project SCCS aware
> (CVS) by the inclusion of
>
> <repository>
> <connection>
> scm:cvs:pserver:[EMAIL PROTECTED]:/src:maven/project4
> </connection>
> </repository>
>
>
> Once a project is SCCS aware, it can then generate all kinds of
> interesting reports as mentioned in my book.
>
> Hope that this helps!
>
> -- Milind
>
> >From: Brett Porter <[EMAIL PROTECTED]>
> >Reply-To: Brett Porter <[EMAIL PROTECTED]>
> >To: Maven Users List <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> >Subject: Re: questions about cvs and maven
> >Date: Wed, 22 Dec 2004 09:11:21 +1100
> >
> > > I'm a little confused on how cvs is being used in maven, I really
> > > appreciate it if anyone can clarify a few things for me. For my
> > > project, we had an ant script that first checkout a module from
> > > our cvs repository to a build directory and then executed the
> > > build process from that directory. Does Maven also work this way?
> >
> >It doesn't have to, but can.
> >
> >Try:
> >maven scm:perform-release
> >
> > > I had placed similar codes like the following into my project.xml.
> > > I'm not sure what these lines exactly does.
> > > <repository>
> > > <connection>
> > >
> > > scm:cvs:pserver:[EMAIL PROTECTED]:/src:maven/project4
> > > </connection> </repository>
> >
> >It is used for the scm goals, and also for generating the changelog
> >reports, and so on.
> >
> > > In addition, do we use the folloiwng command to check out a module
> > > from the cvs repository?
> > > maven scm:checkout-project
> > > -Dmaven.scm.method=cvs
> > > -Dmaven.scm.cvs.module=project4
> > >
> > >
> -Dmaven.scm.cvs.root=:pserver:[EMAIL PROTECTED]:/home/cvspublic
> -Dmaven.scm.checkout.dir=. >
> >Yes, though the next version will use a shorter version such as:
> >maven scm:checkout
> >-Dmaven.scm.url=scm:cvs:pserver:[EMAIL PROTECTED]:/home/cvspublic:
> project4 >
> >Cheers,
> >Brett
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]