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: [email protected] > For additional commands, e-mail: [email protected] > >
