I've got several projects that provide additional configuration of standard Maven plugins (like the compiler plugin or the jar plugin), most commonly changing the source and target values for the compiler plugin. Unfortunately, I get the following warnings:
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-surefire-plugin is missing. [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. I know (and approve of) Maven 3.0 requiring versions on plugins, but shouldn't these particular plugins have versions specified in the super-pom that get merged into the references in my projects? Is it expected behavior that to add configuration to these plugins that I go find out which version of the plugin is in the super-pom and add it again? I can get rid of these warnings by simply putting the appropriate plugin version information in a common parent pom's pluginManagement section, but I'm not sure that I should need to. It just seems odd that I need to repeat the version info if I add some configuration to the plugin in a project, but another project that just uses the plugin as-is through inheritance from the super-pom works without warnings... it should have warnings in both or neither. -- SELECT * FROM users WHERE clue > 0 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
