As discussed on the user-list: >> > > > On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen >> > > > <[email protected]> wrote: >> > > > > Hello, >> > > > > >> > > > > I know that with SVN the developerConnection and connection are >> > > > > updated to the "real" URL, that is when I invoke release:prepare >> > > > > with >> > > > > a URL like: >> > > > > https://SVNSERVER/svn/REPO/myproject/branches/release it will be >> > > > > replaced by >> > > > > https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0 >> > > > > which is fine because now I know which revision to checkout for >> > > > > building the release. >> > > > > >> > > > > With git there is no such possibility to realize this with >> > > > > rewriting >> > > > > the URL AFAIK. So I would have expected however, that maybe the >> > > > > <tag> >> > > > > element would be updated to reflect the fact, that the pom is the >> > > > > one >> > > > > of release, either to the "symbolic name" myproject-1.0 or to the >> > hash >> > > > > of the tag. >> > > > > >> > > > > Regards Mirko
I opened http://jira.codehaus.org/browse/SCM-655. As I want give it a try to implement this (at least for GIT) two questions now: - What is preferable, symbolic tag name or hash? - Is is feasible to implement such behavior in one provider only or should it be part of all (DVCS-)providers? Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
