Re: SCM Tagging / Releasing

2005-09-29 Thread Thomas Van de Velde
Craig, I assume you've not been using the Berkley backend, right? Thomas On 9/29/05, Craig S. Cottingham <[EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Sep 29, 2005, at 11:52, Ralph Pöllath wrote: > > > Inconsistencies should not be possible at all using SV

Re: SCM Tagging / Releasing

2005-09-29 Thread Craig S . Cottingham
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 29, 2005, at 11:52, Ralph Pöllath wrote: Inconsistencies should not be possible at all using SVN. Agreed. As I said earlier, though, "never say never". In the 2+ years I've been using SVN, I've had very few problems with the repository en

Re: SCM Tagging / Releasing

2005-09-29 Thread Ralph Pöllath
MAIL PROTECTED] Sent: Thursday, September 29, 2005 9:46 AM To: users@maven.apache.org Subject: SCM Tagging / Releasing I'd like to know whether tagging with SCM is problematic with concurrent access. Say, I want to make a release, and while SCM is running and does its job, some develop

Re: SCM Tagging / Releasing

2005-09-29 Thread Craig S . Cottingham
CTED] Sent: Thursday, September 29, 2005 9:46 AM To: users@maven.apache.org Subject: SCM Tagging / Releasing I'd like to know whether tagging with SCM is problematic with concurrent access. Say, I want to make a release, and while SCM is running and does its job, some developer commits a patch

RE: SCM Tagging / Releasing

2005-09-29 Thread David Jackman
have it tag the latest version without regard for what's present locally), but I can't imagine why it wouldn't. ..David.. -Original Message- From: Michael Böckling [mailto:[EMAIL PROTECTED] Sent: Thursday, September 29, 2005 9:46 AM To: users@maven.apache.org

SCM Tagging / Releasing

2005-09-29 Thread Michael Böckling
Hello, I'd like to know whether tagging with SCM is problematic with concurrent access. Say, I want to make a release, and while SCM is running and does its job, some developer commits a patch to the repository. What happens? Do I get an inconsistent state, or is that impossible (be it with CV

RE: scm tagging!!!

2005-08-04 Thread Yann Le Du
You must specify the maven.scm.tag, is it what you are already doing ? maven scm:tag -Dmaven.scm.tag=MAVEN_1_0 ( http://maven.apache.org/reference/plugins/scm/commontasks.html ) Do you get an error ? Regards, Yann --- NIRMALA Manivasagam <[EMAIL PROTECTED]> a écrit : > Hi, > > Iam trying to

scm tagging!!!

2005-08-04 Thread NIRMALA Manivasagam
Hi, Iam trying to execute maven scm:tag for that what settings i should place in build.properties. can anyone help me? Thanks, Nirmala Confidentiality Statement: This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential inform

Re: scm tagging!!

2005-08-01 Thread Thomas Van de Velde
ated in C:\cvsnt\source ...what should i > change? > > > > -Original Message- > > From: Gisbert Amm [mailto:[EMAIL PROTECTED] > > Sent: Monday, August 01, 2005 12:57 PM > > To: Maven Users List > > Subject: Re: scm tagging!! > > > >

Re: scm tagging!!1

2005-08-01 Thread Thomas Van de Velde
This doesn't look like a valid CVS root. Nirmally it looks like scm:cvs:local:ignored:/cvs/root:module-name See http://maven.apache.org/reference/project-descriptor.html#class_Repository On 8/1/05, NIRMALA Manivasagam <[EMAIL PROTECTED]> wrote: > > Hello, > > Iam getting this one as an error

scm tagging!!1

2005-08-01 Thread NIRMALA Manivasagam
Hello, Iam getting this one as an error my build.properties : maven.scm.cvs.module=petstore #maven.scm.cvs.url=scm:cvs:local:/cvs/source:petstore maven.compile.deprecation=on maven.scm.url=:local:/cvsnt/source D:\maven1.0.2\bin>maven scm:checkout __ __ | \/ |__ _Apache__ ___ | |\/| / _

Re: scm tagging!!

2005-08-01 Thread Gisbert Amm
Manivasagam wrote: yes my CVS root dir is located in C:\cvsnt\source ...what should i change? -Original Message- From: Gisbert Amm [mailto:[EMAIL PROTECTED] Sent: Monday, August 01, 2005 12:57 PM To: Maven Users List Subject: Re: scm tagging!! Is your CVS root directory probably located

RE: scm tagging!!

2005-08-01 Thread NIRMALA Manivasagam
yes my CVS root dir is located in C:\cvsnt\source ...what should i change? -Original Message- From: Gisbert Amm [mailto:[EMAIL PROTECTED] Sent: Monday, August 01, 2005 12:57 PM To: Maven Users List Subject: Re: scm tagging!! Is your CVS root directory probably located at C:\cvsnt\source

Re: scm tagging!!

2005-08-01 Thread Sanjay Choudhary
Hi scm:cvs:local:/cvsnt/source:petstore:petstore you are specifying petstore:petstore twice. either it should be scm:cvs:local:/cvsnt/source:petstore or scm:cvs:local:/cvsnt/source/petstore:petstore Depends on your repository and module name. -Sanjay On 8/1/05, NIRMALA Manivasagam <[EMA

Re: scm tagging!!

2005-08-01 Thread Gisbert Amm
Is your CVS root directory probably located at C:\cvsnt\source or something like that? /cvsnt/source is a UNIX path and your repository is obviously not located there (the CVSROOT directory within a CVS repository contains the administrative files; CVS needs them to work). Regards, Gisbert Amm

Re: scm tagging!!

2005-08-01 Thread Brett Porter
/cvsnt/source is not a valid CVS repository on your machine. - Brett On 8/1/05, NIRMALA Manivasagam <[EMAIL PROTECTED]> wrote: > Hi all, > > when iam trying to checkout a project iam getting the following error.can > anyone help me? > > > D:\maven1.0.2\bin>maven scm:checkout > __ __ > | \/

scm tagging!!

2005-08-01 Thread NIRMALA Manivasagam
Hi all, when iam trying to checkout a project iam getting the following error.can anyone help me? D:\maven1.0.2\bin>maven scm:checkout __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 build:start: scm:find-connection:

SCM Tagging in Maven 1.0.2

2005-04-21 Thread GOKULAM Jayaram
Hi all, I would like to checkout a module with a particular version of it. For example I want to checkout petstore version 2.0 where the CVS has petstore of different versions. May I know how to get this done? Thanks in advance, Jayaram Confidentiality Statement: This message