maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Rau (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MSITE-171) Site plugin uses plain dependencies for reactor projects instead of results of earlier modules
Date Mon, 07 Aug 2006 22:58:09 GMT
    [ http://jira.codehaus.org/browse/MSITE-171?page=comments#action_71791 ] 
            
Alex Rau commented on MSITE-171:
--------------------------------

I've done some more research on this issue and the use case is somehow more complicated than
described in the first comment.

The problem arises when "mvn site" is issued without a "mvn clean install" before and -Dmaven.test.failure.ignore=true
is used.

The issue can be reproduced as follows:

- Create two projects with some java sources where project b uses a class from project a and
both projects compile without errors.
- Deploy project a with an interface change which affects project B directly without using
a reactor build (mvn deploy in project a's directory). This results in an incompatible artifact
of project A for project B. This is used in this example for determination if project a is
really compiled in the reactor build and used for project b.
- Undo the interface change on Project A in the source code only without installing/deploying
- Project b can therefore only be build during site generation if project a is really locally
rebuilt before and its result is used in the same compile execution of the reactor project
(due to the ignore flag for the unit tests it should be used)
- Add a unit test to project A which fails (not due to compile errors but due to failing assertions)
- mvn site falls back to the artifact in the repository (locally and globally) due to the
occured test failures in project a's unit tests
- mvn site fails due to the fall-back artifact in the repository being incompatible regarding
the public interface

A workaround for this problem is to always do a "mvn clean install" before "mvn site". however
as this is not obvious I would consider this a bug.


> Site plugin uses plain dependencies for reactor projects instead of results of earlier
modules
> ----------------------------------------------------------------------------------------------
>
>                 Key: MSITE-171
>                 URL: http://jira.codehaus.org/browse/MSITE-171
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-5
>         Environment: Win XP, Linux
>            Reporter: Alex Rau
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message