Actually... it's not the super-pom. It's the lifecycle definitions.
See here:
https://maven.apache.org/ref/3.3.9/maven-core/default-bindings.html
You can see which plugins (and which goals in those plugins) are bound to
which phase for a given lifecycle. For example, the jar lifecycle is:
<phases>
<process-resources>
org.apache.maven.plugins:maven-resources-plugin:2.6:resources
</process-resources>
<compile>
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
</compile>
<process-test-resources>
org.apache.maven.plugins:maven-resources-plugin:2.6:testResources
</process-test-resources>
<test-compile>
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile
</test-compile>
<test>
org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test
</test>
<package>
org.apache.maven.plugins:maven-jar-plugin:2.4:jar
</package>
<install>
org.apache.maven.plugins:maven-install-plugin:2.4:install
</install>
<deploy>
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
</deploy>
</phases>
On Sun, Jul 3, 2016 at 5:59 PM Alex Ditu <[email protected]> wrote:
> Hello,
>
> Can anyone provide some help regarding plugin versions? I want to use
> the latest version of maven-war-plugin (or at least one greater than
> 2.3); so i decided to install the latest version of maven, 3.3.9.
> But when I execute "mvn help:effective-pom" I see it still uses 2.3
> version of maven-war-plugin.
> My first question is: where does maven read wich plugin version to
> use, if I don't specify one?
> I tought it was in the super-pom, but I didn't find anything
> there...Can anyone help me understand what is happening?
>
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>