I get the benefits (and costs) vs freestyle - it just seems odd that it's limited to only one invocation per job (and you have to know this up front, in order to stereotype your job as a 'maven' build).
It'd make more sense to me if it were just a 'build with maven' step, that you tick a checkbox for 'build with jenkins monitoring' (or whatever) to get the value-add . That way if you find it's broken, you just untick the box, rather than having to recreate the entire job.. On Sun, Jul 21, 2013 at 3:26 PM, Stephen Connolly < [email protected]> wrote: > Because the maven job type is stupid... But has an alluring per-module > reporting that is a sirens call to users. > > I have been a sting advocate for freestyle+maven build step since 2007 > though, so I may be biased... But all the issues I see repeatedly > re-enforce my bias :-P > > > On Sunday, 21 July 2013, Nigel Magnay wrote: > >> Is there a reason why (non-freestyle) maven builds have to have their own >> build type? >> >> It seems very odd that you can have 1, and only 1 'native' maven build, >> and the rest have to use the 'other', freestyle job type. So if your build >> requires more than one invocation of mvn, you only get to choose one step >> for native.. >> >> >> On Wed, Jul 17, 2013 at 10:33 AM, Stephen Connolly < >> [email protected]> wrote: >> >>> On 17 July 2013 10:23, Olivier Lamy <[email protected]> wrote: >>> >>>> Hi Folks, >>>> Due to some non backward compat changes in maven core 3.1.x, this >>>> doesn't work anymore. >>>> Yes I know some of you (at least I know one!) think this need to be >>>> rewrite. >>>> >>> >>> (I know one == me) >>> >>> I don't think is needs to be rewritten... I think it needs to be taken >>> out round the back and shot... FreeStyle + Maven Build Step all the way man! >>> >>> >>>> >>>> BTW I don't have enough time for the moment to fully rewrite this (but >>>> some ideas :-)) >>>> So in order to take care of users, I will work this weekend on the >>>> current plugin to have it working with 3.1.x. >>>> >>>> Cheers, >>>> -- >>>> Olivier Lamy >>>> Ecetera: http://ecetera.com.au >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Jenkins Developers" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>>> >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > -- > Sent from my phone > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
