Re: How to best define .m2 local maven repo path in multi-branch projects/Jenkinsfile?

_NAME}/.repository") { > // Run the maven buildsh "mvn clean package" > > } > > Since we're "mvn install"-ing snapshots, we cannot reuse the same .m2 repo > for different branches... > > > On Tue, Aug 16, 2016 at 10:25 PM, Álvaro Lobat

Re: How to best define .m2 local maven repo path in multi-branch projects/Jenkinsfile?

Hello Stefan, An easy way to do it is to use the new Pipeline Maven plugin. It allows you to define a local maven repository, relative to to the workspace of the job or with an absolute path, you can also use shell variables

Re: New Pipeline Maven plugin

At the moment > i am using the 'bat' to call the goals for release:prepare and > release:perform > > > > Thanks > > > > > > > On Thu, Aug 11, 2016 at 11:33 AM, Álvaro Lobato <alvaro...@gmail.com > > wrote: > >> >> Hello everyone, &g

Re: New Pipeline Maven plugin

Yes, thanks Daniel. -- 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

New Pipeline Maven plugin

Hello everyone, I'd like to introduce you to the new Pipeline Maven plugin . The intention of this plugin is to help using maven from pipeline, setting up a maven environment by using a withMaven step. This environment can