maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Koch (JIRA)" <>
Subject [jira] (MSITE-640) Maven searches only central repository for imported dependencies
Date Thu, 06 Jun 2013 06:11:03 GMT


Michael Koch commented on MSITE-640:

I should add that I could not reproduce the error in the current Maven 3.1-SNAPSHOT. The newer
Aether version (_Eclipse 0.9.0-M2_ as opposed to _Sonatype 1.13.1_ in the 3.0.5 release) resolves
the artifact from the local repository even though the remote repository from which it originated
is not defined in the {{ProjectBuildingRequest}}.
> Maven searches only central repository for imported dependencies
> ----------------------------------------------------------------
>                 Key: MSITE-640
>                 URL:
>             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:
> 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
For more information on JIRA, see:

View raw message