Well if you wanted to explore this, the way I would come at this is via maven's toolchains api
Thus if the SCM tool had an entry for the HG executable in ~/.m2/toolchains.xml then that path would be used, otherwise whatever is resolved from the path would get resolved. Working on this will likely help flesh out the parts of the toolchains api that are slightly undercooked, but I would be happy to review and try and help (though I do not have time at present to write the code myself) I think this would be a good sized problem for somebody in the committer school (or wanting to enrole) -Stephen On Thursday, 20 December 2012, cowwoc wrote: > Gentlemen, > > I'd like to reopen this discussion. Automated build systems like Jenkins > need to run out of a self-contained sandbox. As such, we need to be able to > specify the full path to Mercurial. I filed this bug report against > Jenkins: > https://issues.jenkins-ci.org/browse/JENKINS-16151 > > but I believe this can only be implemented with help from Maven SCM. Can > someone from the Maven team please comment on this? > > Thank you, > Gili > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-to-specify-full-path-of-a-executable-for-a-scm-vendor-tp5463712p5739204.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org <javascript:;> > For additional commands, e-mail: users-h...@maven.apache.org<javascript:;> > >