maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Theussl (JIRA)" <>
Subject [jira] Commented: (MSITE-548) site:deploy -> folder structure is different when artifactId=module's directory
Date Tue, 01 Feb 2011 08:19:59 GMT


Lukas Theussl commented on MSITE-548:

There are several issues here. First I cannot quite reproduce your problem (running maven
2.2.1, site-plugin-2.3-SNAPSHOT): the deployed directory structure is


(ie modules get deployed to the same level) while it should actually be


However, this is apparently not a site-plugin issue, running help:effective-pom in one of
the modules shows that the effective of the module is actually
/tmp/module1, this is what the site plugin uses.

Anyway, for such non-standard project layouts I would recommend to specify the distMngmnt
sections for each module explicitly, doing so the deployed site is ok AFAICS.

> site:deploy -> folder structure is different when artifactId=module's directory
> -------------------------------------------------------------------------------
>                 Key: MSITE-548
>                 URL:
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0-beta-3
>         Environment: windows
>            Reporter: Stefan Hansel
>         Attachments:
> There is a multimodule flat project structure:
> root
> module1
> module2
> module1 has an artifactID of 'module1'  (same as directory name)
> modulu2 has an artifactID of 'module-2' (different to directory name)
> After a 'mvn site-deploy' the generated report has the folder structure:
> /root
> /root/module-2
> /module1
> So based on the artifactID the submodules are created as a child of the root - or not.
> This is at least inconsistent and should be changed to be handled always the same - independent
of the artifactID.
> This is also important for other plugins (i.e. the dashboard plugin).
> They seem to have some hardcoded directory structure (preferring submodules as childs
of the root report). 
> Due to this bug (see the links between reports
there still don't work as long as artifactID=module's directory. 
> Attached you will find a testcase (based on maven3, but can also be used with maven2
when the version of the site-plugin is changed).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message