[
http://jira.codehaus.org/browse/MNG-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5000.
----------------------------------
Resolution: Not A Bug
Assignee: Benjamin Bentmann
bq. (ie modules get deployed to the same level)
Which is the expected behavior as per MNG-3134 and the structure of the example
project.
bq. [...] running help:effective-pom in one of the modules shows that the
effective distributionManagement.site.url of the module is actually
/tmp/module1, this is what the site plugin uses.
This is what I see with Maven 3.0.x
{code:xml}
<distributionManagement>
<site>
<id>MSITE-227</id>
<url>file:///tmp/module1/</url>
</site>
</distributionManagement>
{code}
and with Maven 2.2.1:
{code:xml}
<distributionManagement>
<site>
<id>MSITE-227</id>
<url>file:///tmp/module1</url>
</site>
</distributionManagement>
{code}
which apart from the trailing slash from the parent's URL being preserved by
Maven 3.x, is identical. So I don't see how this is 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
