You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/09/06 02:37:06 UTC

[jira] Closed: (MNG-836) plugin dependencies cannot be resolved

     [ http://jira.codehaus.org/browse/MNG-836?page=all ]
     
Brett Porter closed MNG-836:
----------------------------

    Resolution: Fixed

was a regression caused by MNG-757, rolled back

> 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: Brett Porter
>      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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org