[
http://jira.codehaus.org/browse/MNG-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255938#action_255938
]
Stefan Hansel commented on MNG-5000:
------------------------------------
Please don't just close this bug.
There is an issue with the site-plugin under Maven3 creating different pathes
based on the artifact-ID of a module.
The site-plugin developers claim this is a core issue.
As someone from the outside I cannot decide if this is a site-plugin problem
(where I originally filed the bug) or a core issue. But seeing this bug moved
from one project to the other and then seeing it closed is no solution.
Regardless of who's right or wrong regarding the expected final directory
layout: one of both modules is behaving wrong under Maven3.
Please compare the distribution.url (copied from help:effective-pom) of module1
and module2 with Maven3.
{code}
<distributionManagement>
<site>
<id>MSITE-227</id>
<url>file:///tmp/module1/</url>
</site>
</distributionManagement>
{code}
{code}
<distributionManagement>
<site>
<id>MSITE-227</id>
<url>file:///tmp/MSITE-227/module-2/</url>
</site>
</distributionManagement>
{code}
Here module1 adheres to the flat layout, while module2 uses a nested layout.
So if flat-layout is the expected one, then module2 is behaving wrong!
Please reconsider closing this bug (or at least move it back to the site-plugin
of you don't think it's a core issue).
> child distributionManagment.site.url not correct in a flat directory layout
> ---------------------------------------------------------------------------
>
> Key: MNG-5000
> URL: http://jira.codehaus.org/browse/MNG-5000
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: windows
> Reporter: Stefan Hansel
> Assignee: Benjamin Bentmann
> 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
