ah of course - makes sense
but here's an interesting q then...
we are setting up continuum to build our m2 projects. i'd like continuum to check out the code from CVS, build it, build the site, deploy the site, generate notification emails and generate a snapshot release. all using the same pom.xml file as any developer would.
is that 'best practice'or am i missing some key concept? if so then how would i prevent 'any old developer' from running mvn release?
Kind regards,
Dave Sag
Kenney Westerhof <[EMAIL PROTECTED]> wrote on 12-12-2005 14:56:23:
> On Mon, 12 Dec 2005, David Sag wrote:
>
>
> No; you can specify the username/password in ~/.m2/settings.xml
> in a <server> tag.
> I'm not really sure a password is needed for svn/cvs; if you logged in
> once on the command line the password is stored in ~/.subversion/ or
> ~/.cvspass, but I'm not sure the scm code uses that (yet).
>
> -- Kenney
>
> > Does this imply i need to put a username and password into my pom.xml as
> > hard coded params?
> >
> > Kind regards,
> > Dave Sag
> >
> >
> >
> >
> >
> >
> > Jean-Charles Giardina <[EMAIL PROTECTED]> wrote on 08-12-2005
> > 10:59:29:
> >
> > > The correct scm URL format is :
> > >
> > > scm:cvs:pserver:[username[:[EMAIL PROTECTED]:port]:
> > > path_to_repository:module_name
> > >
> > > For your example that mean :
> > >
> > > scm:cvs:pserver:[EMAIL PROTECTED]:/r:m
> > >
> > > don't miss the first '/' at repository path
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
>
> --
> Kenney Westerhof
> http://www.neonics.com
> GPG public key: http://www.gods.nl/~forge/kenneyw.key
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
