Files that come and go also include the SCM tools installed on the build slave by Jenkins. And Jenkins should put the paths it is injecting into toolchains in the build log anyway, so I don't see your point about files as being an argument winner.
Also a toolchains file allows the developer to set up for their machine and "just work" whereas the cli requires a lot if typing or setting up some alias. Given that toolchains is already there for JDK and JRE I see that the "right thing" (iow the maven way) is to use toolchains. - Stephen On Friday, 21 December 2012, cowwoc wrote: > > Files come and go. The build log may stick around for months after > the workspace itself is gone. For this reason, I still favor > command-line arguments. > > Gili > > On 21/12/2012 12:26 PM, stephenconnolly [via Maven] wrote: > > I am not suggesting a *static* file. I am suggesting a dynamic file that > > Jenkins populates and just one already existing cli parameter that works > > with more versions of maven than anything we add now. > > > > - Stephen > > > > On Friday, 21 December 2012, Jesse Glick wrote: > > > > > On 12/20/2012 12:19 PM, cowwoc wrote: > > > > > >> […] in a clustered environment all my configuration sits inside > > Jenkins. > > >> Having > > >> to configure each node before I can use Jenkins on it adds a lot of > > work. > > >> > > >> […] I favor adding command-line options to configuration files. > > >> > > > > > > I agree that for cases like this it would be better to define the > > > Mercurial location using a command-line option (or system property, > > > environment variable, etc.) rather than a static configuration file; > > though > > > it might suffice for Jenkins to augment $PATH before calling Maven. > > > > > > > > > > > ------------------------------**------------------------------**--------- > > > To unsubscribe, e-mail: [hidden email] > > </user/SendEmail.jtp?type=node&node=5739647&i=0> > > > For additional commands, e-mail: [hidden email] > > </user/SendEmail.jtp?type=node&node=5739647&i=1> > > > > > > > > > > > > ------------------------------------------------------------------------ > > If you reply to this email, your message will be added to the > > discussion below: > > > http://maven.40175.n5.nabble.com/How-to-specify-full-path-of-a-executable-for-a-scm-vendor-tp5463712p5739647.html > > > > To unsubscribe from How to specify full path of a executable for a scm > > vendor?, click here > > < > http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5463712&code=Y293d29jQGJicy5kYXJrdGVjaC5vcmd8NTQ2MzcxMnwxNTc0MzIxMjQ3 > >. > > NAML > > < > http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-to-specify-full-path-of-a-executable-for-a-scm-vendor-tp5463712p5739649.html > Sent from the Maven - Users mailing list archive at Nabble.com.
