[ https://jira.codehaus.org/browse/MSITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361888#comment-361888 ] 

Stefan Cordes commented on MSITE-640:
-------------------------------------

...and it is "Unresolved" ;-)

> Maven searches only central repository for imported dependencies
> ----------------------------------------------------------------
>
>                 Key: MSITE-640
>                 URL: https://jira.codehaus.org/browse/MSITE-640
>             Project: Maven Site Plugin
>          Issue Type: Bug
>          Components: Maven 3
>    Affects Versions: 3.0
>         Environment: Windows 7
>            Reporter: Markus Tippmann
>         Attachments: stacktrace.txt
>
>
> We are using dependencyManagement with "import" scope like described here:
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies
> Problem occurs only at site generation, not at build time, where it works perfectly. 
> The site plugin tries to find the imported artifacts, but searches only the central repository and ignores the repositories in settings.xml configuration. Mirror settings work, if "central" is mirrored, but dependencies need to be resolved from two repositories, so one mirror does not help here.
> I try to attach the relevant parts of the stacktrace. 



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)