o Why would a plugin be executing in its own POM. I think this is a far out case and you shouldn't be testing your plugin with its own POM. The comment is "I guess...". I don't think this is right.

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@572868 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jason van Zyl 2007-09-05 03:44:55 +00:00
parent 95759ed0c9
commit 8077fb59ac
1 changed files with 0 additions and 18 deletions

View File

@ -61,15 +61,6 @@ public class DefaultPluginVersionManager
// TODO: Revisit to remove this piece of state. PLUGIN REGISTRY MAY BE UPDATED ON DISK OUT-OF-PROCESS!
private Map resolvedMetaVersions = new HashMap();
/**
* @deprecated
*/
public String resolvePluginVersion( String groupId, String artifactId, MavenProject project, ArtifactRepository localRepository )
throws PluginVersionResolutionException, InvalidPluginException, PluginVersionNotFoundException
{
return resolvePluginVersion( groupId, artifactId, project, localRepository, false );
}
public String resolvePluginVersion( String groupId,
String artifactId,
MavenProject project,
@ -135,15 +126,6 @@ public class DefaultPluginVersionManager
getLogger().debug( "Version from RELEASE metadata: " + version );
}
// if we're still empty here, and the current project matches the plugin in question, use the current project's
// version, I guess...
if ( StringUtils.isEmpty( version ) && project.getGroupId().equals( groupId ) &&
project.getArtifactId().equals( artifactId ) )
{
version = project.getVersion();
getLogger().debug( "Version from POM itself (this project IS the plugin project): " + version );
}
// if we still haven't found a version, then fail early before we get into the update goop.
if ( StringUtils.isEmpty( version ) )
{