[ http://jira.codehaus.org/browse/MNG-836?page=all ]
Kenney Westerhof updated MNG-836:
---------------------------------
Description:
Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
Somehow plugin dependencies are not resolved; weird that this doesn't occur
more often.
This is because in DefaultPluginManager the verifyPlugin method calls
checkRequiredMavenVersion
with just the PluginArtifactRepositories. The checkRequiredMavenVersion
resolves the plugin and/or
its dependencies but does not have access to the normal artifact repositories,
so only plugin repositories
can be searched for the plugin's dependencies.
Modified the verifyPlugin method to add the RemoteArtifactRepositories to the
list.
was:
Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
Since the snapshots id is used on both the normal and the plugin repositories,
maven-modello-plugin's dependencies cannot be resolved. Maven-modello-plugin
comes from snapshots..../plugins/ and it's dependencies are in snapshots..../.
Renaming the pluginRepository with id snapshots to something else fixes this,
but there seems to be a mixup in plugin repo's and artifact repo's.
Fix Version: 2.0-beta-1
Component: maven-core
Remaining Estimate: 1 hour
Original Estimate: 3600
Summary: plugin dependencies cannot be resolved (was: plugin
dependencies cannot be resolved when repository has same <id>.)
First I thought this was because of a duplicate repository <id>; changing it
fixed it. But I couldn't
reproduce it again, and after fixing it it was something else; so I renamed
this issue.
> plugin dependencies cannot be resolved
> --------------------------------------
>
> Key: MNG-836
> URL: http://jira.codehaus.org/browse/MNG-836
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Assignee: Kenney Westerhof
> Fix For: 2.0-beta-1
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
> Somehow plugin dependencies are not resolved; weird that this doesn't occur
> more often.
> This is because in DefaultPluginManager the verifyPlugin method calls
> checkRequiredMavenVersion
> with just the PluginArtifactRepositories. The checkRequiredMavenVersion
> resolves the plugin and/or
> its dependencies but does not have access to the normal artifact
> repositories, so only plugin repositories
> can be searched for the plugin's dependencies.
> Modified the verifyPlugin method to add the RemoteArtifactRepositories to the
> list.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
