[jira] (MSITE-171) Site plugin uses plain dependencies for reactor projects instead of results of earlier modules

["Florian Brunner (JIRA)" <ji...@codehaus.org>]

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

Florian Brunner commented on MSITE-171:
---------------------------------------

36 votes! Any updates?

> Site plugin uses plain dependencies for reactor projects instead of results of earlier modules
> ----------------------------------------------------------------------------------------------
>
>                 Key: MSITE-171
>                 URL: https://jira.codehaus.org/browse/MSITE-171
>             Project: Maven Site Plugin
>          Issue Type: Bug
>          Components: multi module
>    Affects Versions: 2.0-beta-5
>         Environment: Win XP, Linux
>            Reporter: Alex Rau
>         Attachments: install_site_runs.log, site_fails.log, subsequent_site_runs.log
>
>
> When creating a multi-module site the site plugin uses dependencies from related modules from the repository instead of using artifacts from the same execution.
> That causes inconsistent reports on the sites. An example:
> Project A has modules B and C defined. B is build first and a site for project B is created. Then project C is build using a dependency either from the local or remote repository. Therefore the site contains results which rely on a build with an "out-dated" artifact used as dependency. This leads to plainly wrong results when examining surefire-reports as Project C should have been build with the (current) artifact of project B (taken from the same execution of the site plugin).



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