[
https://jira.codehaus.org/browse/MSITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297616#comment-297616
]
Edward Winston commented on MSITE-640:
--------------------------------------
We recently ran into this problem as well. It was confusing because it was
working on my local machine and not on the server. As a work around, it
appears that if the parent pom in question is installed in your local
repository instead of retrieved from a remote repository things will work.
This means that in you ${HOME}/.m2/repository directory find the artifact in
question. Then change the file _maven.repositories to not have the location
from where the pom was downloaded. In our case the file went from this :
bq. parent-pom-1.pom>central=
to this :
bq. parent-pom-1.pom>=
After this change it all worked.
> Maven searches only central repository for imported dependencies
> ----------------------------------------------------------------
>
> Key: MSITE-640
> URL: https://jira.codehaus.org/browse/MSITE-640
> Project: Maven 2.x and 3.x 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
