[
http://jira.codehaus.org/browse/MSITE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Hansel updated MSITE-548:
--------------------------------
Attachment: artifact-id-testcase.zip
> site:deploy -> folder structure is different when artifactId=module's
> directory
> -------------------------------------------------------------------------------
>
> Key: MSITE-548
> URL: http://jira.codehaus.org/browse/MSITE-548
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Affects Versions: 3.0-beta-3
> Environment: windows
> Reporter: Stefan Hansel
> Attachments: artifact-id-testcase.zip
>
>
> 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 http://jira.codehaus.org/browse/MOJO-1630) 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
