Yes 2009/4/1 Todd Thiessen <[email protected]>
> Consider your response acknowledged ;-). > > We may be moving to 1.6 soon (on the server side). Would a 1.6 client > work with a 1.5 server? > > --- > Todd Thiessen > > > > -----Original Message----- > > From: Stephen Connolly [mailto:[email protected]] > > Sent: Wednesday, April 01, 2009 4:53 PM > > To: Maven Users List > > Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released > > > > Has anybody tried switching from neon to serf as the > > repository access method??? > > > > I read on the svn list that 1.5.1+ WC->URL tagging for > > http/https repositories works with serf but not neon > > > > I have not been able to try this yet as it would mean > > recompiling my client. > > > > This is a client only setting and does not affect the server. > > > > the 1.6.0 binaries from collabnet include both serf and neon > > transports and you can switch between them using one of the > > config files. > > > > tagging works with svn, and ssh+svn repos no problem > > > > (I keep saying this because nobody seems to be acknowedging > > me saying this > > ;-) ) > > > > -Stephen > > > > 2009/4/1 Todd Thiessen <[email protected]> > > > > > > > > > > The part where it says how to make a complex tag. ie: > > making a tag > > > > > from a working copy. > > > > > > > > A complex tag refers to ways of making a "snapshot" of a specific > > > > working copy, quoting specifically "which is an exact snapshot of > > > > your working copy-mixed revisions, URLs, and all". > > > > > > Which is precisely what a complex tag is. > > > > > > > Trying to make a release from such a "snapshot" is a fundamental > > > > contradiction in terms in the maven world, and very bad practice. > > > > > > This is what the maven plugin does (ie: create a tag from > > your working > > > copy), so I am not sure how you can say it is a bad practice in the > > > maven world. You will have to take that up with the maven world I > > > suppose ;-). > > > > > > > > --------------------------------------------------------------------- > > > 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] > >
