[
http://jira.codehaus.org/browse/MNG-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257384#action_257384
]
Lukas Theussl commented on MNG-5000:
------------------------------------
bq. such a layout is a recipe for trouble as it results in effective URLs that
depend on the source of the POM (project vs repo)
If this is true then there must be something wrong with Maven... ;)
bq. it would see different URLs than those used when building the project
I don't understand why this should be the case, are there any docs or examples
you could point me to? The state of a pom should be uniquely specified by its
maven coordinates and those of its parent, not by the module structure of the
build. In other words, why shouldn't it be possible to move a module into a
different directory, without changing the module's identity?
> [regression] child distributionManagment.site.url not correct in a flat
> directory layout when child's artifactId doesn't match its module name
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> 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
> Fix For: 3.0.3
>
> 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
