1

Maven by default uses these versions of plugins such as clean, compile, jar etc. if I don't override them in my pom.xml.

Should I be using more recent version of these plugins? For example, the current version of maven-compiler-plugin is 3.6.1 while the default is 2.5.1. Or, are the default versions reasonable enough that anyone not consciously depending on newer features need worry?

antak
  • 19,481
  • 9
  • 72
  • 80
  • What exactly is it that you're trying to achieve and is not available with `2.5.1`? Could possibly be similar to http://stackoverflow.com/questions/40927845/is-there-a-way-to-update-default-bindings-xml-for-maven-on-local ? – Naman Mar 15 '17 at 03:49
  • @nullpointer I have no idea what you *can't* achieve in 2.5.1, let alone why I should update to 3.6.1.. "*Are default versions reasonable enough that anyone not depending on newer features need not worry about updating*" is the question. "Reasonable" can be in terms of stability of build, build performance, or gotchas that may have been fixed in newer versions. – antak Mar 15 '17 at 05:46
  • Best is to define via pluginManagement the newest versions of the plugins. If you have issues with it downgrade versions...It is important to define the versions via pluginManagement to be safe during an Maven update... – khmarbaise Mar 15 '17 at 13:33

1 Answers1

1

The maven way is "convention over configuration", so if you're wondering about not using the default parameters when running a maven build, you should have a specific use case that is not covered by the default version.

Here for example, (according to here) the install plugin is still at version 2.5.2, so that would point to me that using 2.5.1 is not such a bad choice by default.

I think the biggest difference comparing version (I might be wrong) is the upgrading of compatible version as for example this pseudo release note of the maven compiler.

Adonis
  • 4,670
  • 3
  • 37
  • 57