Fixing case where parent pom has pluginManagement, child does not refer to the plugin, and plugin is used directly on the command line...version from parent-pom pluginManagement should be used. Test case to follow.

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@599338 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
John Dennis Casey 2007-11-29 08:42:38 +00:00
parent 941a11381c
commit 9732014c53
1 changed files with 3 additions and 0 deletions

View File

@ -211,6 +211,7 @@ final class BindingUtils
plugin = new Plugin();
plugin.setGroupId( binding.getGroupId() );
plugin.setArtifactId( binding.getArtifactId() );
plugin.setVersion( binding.getVersion() );
}
injectPluginManagementInfo( plugin, project );
@ -238,6 +239,7 @@ final class BindingUtils
configuration = mergeRawConfigurations( reportConfig, configuration );
}
binding.setVersion( plugin.getVersion() );
binding.setConfiguration( configuration );
}
@ -308,6 +310,7 @@ final class BindingUtils
Map plugMgmtMap = buildPluginMap( plugMgmt );
String key = createPluginKey( plugin );
Plugin mgmtPlugin = (Plugin) plugMgmtMap.get( key );
if ( mgmtPlugin != null )