[
https://jira.codehaus.org/browse/MSITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341914#comment-341914
]
Jim Hurne commented on MSITE-640:
---------------------------------
It has been two years since this bug was opened, and it is still a problem.
That means that people are ether downgrading to 3.3 of the maven-site-plugin,
or are implementing crazy workarounds like manually editing files in the
.m2/repository directory, and have been doing so for two years.
Michael Koch suggested a fix in this earlier comment:
http://jira.codehaus.org/browse/MSITE-640?focusedCommentId=326248&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-326248
Any chance someone could look at the fix suggested by Michael? Is there
anything else myself or the community can do to move this bug forward?
> 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)
