[
http://jira.codehaus.org/browse/MNG-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259314#action_259314
]
Lukas Theussl commented on MNG-5000:
------------------------------------
I'm still confused about this... Benjamin: what's the actual algorithm to
calculate the effective url if it gets inherited? The current [site
docs|http://maven.apache.org/plugins/maven-site-plugin/usage.html] say:
{noformat}
If subprojects inherit the site URL from a parent POM, they will automatically
append their <artifactId> to form their effective deployment location.
{noformat}
This is what I always had in mind but it is obviously not correct for the
attached test project (the modules get deployed into the same directory as
root, instead of having their artifactId appended). At least the behavior is
consistent now AFAIS so I guess the docs need to be adjusted.
> [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
