The lifecycle defines the version to use, but if you edit your pom to use a different version it will take precedence from what I've experienced.
Editing the pom I believe this is a better solution as otherwise different developers or different machines might behave differently. Where as if the pom in source control has the version specified it will be the same version of all builds. John On 04/07/2016, alexd92 <ditu.alexan...@gmail.com> wrote: > Thank you for the info. I'll set the version in the parent pom (I believe > is > the simplest solution). > I've read about > https://maven.apache.org/ref/3.3.9/maven-core/default-bindings.html and now > I realized it is packed in maven-core.jar (I thought it is editable..). > > Is there another way to upgrade a plugin version instead of editing the > pom? > Is not possible to specify this at global level (somewhere in maven > installation folder)? > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-does-maven-choose-which-plugin-version-to-use-tp5874198p5874202.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
