[
https://jira.codehaus.org/browse/MSITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297128#comment-297128
]
Richard Eggert commented on MSITE-640:
--------------------------------------
I'll try to put together an example that I can attach here when I find some
time, but here's how to reproduce the problem for the parent POM use case:
In your active profile in settings.xml, configure a remote repository that
points to a location in your local file system. Make sure that the central
repository is independently reachable (either directly or via a configured
mirror).
Create a new Maven project with packaging type "pom". Configure the
distributionManagement section such that "mvn deploy" will target the "remote"
repository on your file system that you configured in settings.xml. Run "mvn
deploy" on this project, then delete your local repository (but not the
"remote" one that you deployed to).
Create a second Maven project with packaging type "pom". Use the first project
configured above as the "parent" POM, but set the relativePath element to be
empty (forcing it to be resolved via repository). In the "modules" section of
the POM, specify a sub-module.
Within the second Maven project, create the sub-module project that you
specified in the POM, using the containing project's POM as the parent (set
relativePath to "..").
>From within the second Maven project (the container of the sub-module), run
>"mvn package". This should work perfectly. Then run "mvn site". This will
>fail, being unable to resolve the dependency to the parent POM (the first
>project that you deployed) against the central repository (apparently ignoring
>the "remote" repository on the local filesystem, as well as the fact that the
>parent POM was already downloaded into the local repository during "mvn
>package").
Something similar will happen if you specify a build extension in the
sub-module POM.
> 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
