Monday 15 April 2013

java - Maven plugin version not specified -


I have just seen that the version of the plugin is optional in Maven. I can still make my own modules without specifying it. Take an example with the Maven-bundle-plugin.

  & lt; Plugin & gt; & Lt; Group & gt; Org.apache.felix & lt; / Group & gt; & Lt; ArtifactId & gt; Maven Wrap-Plugin & lt; / ArtifactId> & Lt; Extensions & gt; True & lt; / Extensions & gt; .... & lt; / Plugin & gt;   

I have written a simple pom.xml without a parent to try it, so plugin management is not included. I have also confirmed Super Super Palm 4.0.0.xm in the Maven-Model-Builder that the Maven-bundle-plugin is not there. This plugin version is not specified anywhere.

How maven determines which version will it take?

From:

Automatic plugin version resolution < P> When a plug-in was used without a clear version given in POM or on the command line, Maven 2.x was used to make the latest version available where the latest version release or snapshot could be Stability For, Maven 3.x likes the latest release version on the latest snapshot version.

Consistent with the danger of non-productable construction made by the version plugin, this feature is set to be removed, as long as plug-in announcements are related to POM. Users of Maven 3.x will receive this warning when plug-in versions have been found to encourage plug-in versions to be added to POM or their parents' POM. Plugin required for Enforcer Rules Additional usage can be done in POM for further testing for plug-in versions.

No comments:

Post a Comment