An explanation can be found in the Maven 3.x Compatibility Notes:
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-AutomaticPluginVersionResolution
BTW: The version numbers can either be defined in the 'pluginManagement'
and/or in the 'plugins' section - depends on Your project.
On 04/02/11 06:47, Anders Hammar wrote:
A very similar question was asked on the list some weeks ago.
You need to lock down the (specify) the version of maven-compiler-plugin.
You do that in the pluginManagement section. An example is here:
http://maven.apache.org/pom.html#Plugin_Management
(Note: You don't need to specify any executions though.)
/Anders
On Fri, Feb 4, 2011 at 06:16, Jonthan DeMaagd<[email protected]> wrote:
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for org.sonatype.mavenbook.custom:simple-weather:jar:1.0
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 69,
column
12
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
..
..
Project builds and runs fine.
But I really want to take care of these WARNINGS!
Have not had much luck with tutorial, "Maven by Example" or online
resources.
Went to this as last resource!
Thanks much!
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
