Hm, this will be a hard one. I know detected, that the rewrite of the SCM section happens in the maven-release-plugin (org.apache.maven.shared.release.phase.RewritePomsForReleasePhase). Two problemes I encountered now: - The maven-scm-plugin does not seem to implement the equivalent of "scm:info" (there is an implementation in the maven-scm-api, however). - Providing the hash value instead of the symbolic release tag is kind of a chicken-egg scenario: we know the hash only after the rewrite of the pom and the commit, modifying the pom afterwards to include the hash as tag however does create a new hash. So inserting the hash seems to be impossible :-(.
Any thoughts :-)? Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Mon, Dec 19, 2011 at 12:26, Olivier Lamy <[email protected]> wrote: > some scm providers have something implemented. > > for git it's : git rev-parse --verify HEAD > for svn: svn info > for hg: hg id > > more details on those providers in various Info command impls. > > 2011/12/19 Stephen Connolly <[email protected]>: >> On 19 December 2011 10:45, Mirko Friedenhagen <[email protected]> >> wrote: >>> 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? >> >> I fear it has to be hash.... but better would be to have it configurable >> >>> - Is is feasible to implement such behavior in one provider only or >>> should it be part of all (DVCS-)providers? >> >> When you've sent me the pony, then implement it for all DVCS providers >> and check that it is implemented for CVS too >> >>> >>> 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] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > --------------------------------------------------------------------- > 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]
