Forgot to add ... this is in relation to https://issues.jenkins-ci.org/browse/JENKINS-23831 ... but maybe better underlying question is: why does this behaviour exist? is there a good reason? Should it default to _not_ do that and to add an additional option to enable it, or vice versa?
On Thursday, 13 August 2015 01:02:53 UTC-7, Brantone wrote: > > Using Freestyle project rather than Maven-project due to several > recommendations ... ex: as one poster called it : the "evil job type" :-/ > > Except, when calling it via "Invoke top-level maven targets", I see it > passes in ALL build parameters as options, can anyone shed light on why > that'd be the case? Or what benefit that provides? > I guess maybe it makes it easier if it's actually desired, but for just > wanting to do simple build, those extra pre-pended options get clunky ... > furthermore, as far as I can tell, there's no mention in any of the help > dialogues that say that'll occur. > > The nearest I could find is: > > https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tasks/Maven.java#L316 > > ... where it just includes it straight away :( > > Any reasoning, or is it better just to use the Maven job-type ?? > > Thanks in advance. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a6f79969-3209-4374-aec3-8d31754f59d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
