maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MSITE-554) Maven site plugin doesn't not work for not flat modules
Date Sun, 13 Feb 2011 20:12:22 GMT

    [ http://jira.codehaus.org/browse/MSITE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255879#action_255879
] 

Dennis Lundberg commented on MSITE-554:
---------------------------------------

Paul, that's one of the oddest looking project structures I have seen this far. Therefor I
need to start by ask a couple of questions.

Do all the modules A, B, C and D have the same parent?

Why is moduleC inside the moduleB directory?

Why is moduleD inside the someDir directory?

The resolution of parent is a bit different in Maven 3, compared to Maven 2. It relies on
the <relativePath> being set correctly in the <parent> element. Does modules C
and D have this set? They should because they cannot use the default value of ../pom.xml.

> Maven site plugin doesn't not work for not flat modules
> -------------------------------------------------------
>
>                 Key: MSITE-554
>                 URL: http://jira.codehaus.org/browse/MSITE-554
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>          Components: inheritance, Maven 3, multi module, site:run
>    Affects Versions: 3.0-beta-3
>         Environment: Red Hat Enterprise Linux Server release 5.2 (Tikanga) x86_64 x86_64
x86_64 GNU/Linux
>            Reporter: Paul Green
>
> It looks like maven-site-plugin for maven3 does NOT work properly for modules that are
not organized in flat structure.
> Example:
>             <modules>
>                 <module>moduleA</module>
>                 <module>moduleB</module>
>                 <module>moduleB/moduleC</module>
>                 <module>someDir/moduleD</module>
>             </modules>
> Two first modules (moduleA and moduleB) are working fine - all reports are generated
for them.
> Next two (moduleC and moduleD) are NOT working in fact. There is even no index.html page
being generated under:
>   moduleB/moduleC/target/site
> or 
>   someDir/moduleD/target/site
> directories.
> I guess that reason is that for moduleC and moduleD pom.xml are resolved NOT from reactor
BUT from local maven repository.

-- 
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