On Mon, 12 Dec 2005, David Sag wrote: > 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
You usually keep the site up to date with the latest release. If you deploy to snapshot site (i.e. not the main site), this should be ok. Normally continuum itself has a distribution in some directory, so you don't really need to make a snapshot relase - i really think humans should decide that. But it's possible. > would i prevent 'any old developer' from running mvn release? mvn release will require write permissions to the repo to tag it; i guess you can only prevent it partially by disallowing write access to the /tags/ space in the repo (if you're using subversion). The current pom still is updated & committed with the new version.. I might be mistaken, but i think a release also deploys the snapshots to the remote repository. You could easily limit write access to that by not sharing a username/password for the server (and make downloads anonymously available). -- Kenney > 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] > > > -- 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]
