[
http://jira.codehaus.org/browse/MSITE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MSITE-279:
------------------------------------
Attachment: site-directory.patch
Fixing this against maven-doxia-tools is not that easy because the only chance
I see is an API redesign.
Unlike my first approach for the maven-site-plugin, I chose to change the
siteDirectory parameter for the doxia-tools methods to be a string denoting the
*relative* path to the site directory, eg. "src/site", instead of passing
around the base directory of the original project from which the siteDirectory
mojo parameter was taken. Callers of the doxia-tools like the maven-site-plugin
should be able to easily create this string from their (absolute)
java.io.File-based mojo parameter via {{SiteTool.getRelativePath(
siteDirectory.getAbsolutePath(), basedir.getAbsolutePath() )}}. Doing this once
in the plugin for the *current* project and not for each ancestor project is
the key to fix the issue.
Of course, a relative path could be encoded via java.io.File as well but I see
the risk that people errorneously pass in absolute paths that they got from
Maven's path translation.
BTW, [JUnit
assertions|http://junit.sourceforge.net/javadoc/junit/framework/Assert.html]
are written in the order (expected, actual).
> Inheritance of elements from site descriptor quite broken
> ---------------------------------------------------------
>
> Key: MSITE-279
> URL: http://jira.codehaus.org/browse/MSITE-279
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: inheritance
> Affects Versions: 2.0-beta-6
> Environment: Maven 2.0.8, JDK 1.5.0_12, WinXP
> Reporter: Benjamin Bentmann
> Priority: Critical
> Attachments: project.zip, site-directory.patch, site-directory.patch
>
>
> After updating to 2.0-beta-6, I never get proper site output for multi module
> projects. I attached a simple dummy project that shall help to reproduce the
> problem.
> When I perform a reactor build of the site (i.e. "project-parent> mvn site"),
> the pages of the sub module project-module-1 properly inherit most of the
> decorator elements, except for the custom "overview" menu. That is, the site
> of the sub module contains the menu configured for the parent project despite
> the sub module specifying its own menu.-
> In contrast, when I only build the site of the sub module (i.e.
> "project-module-1> mvn site"), many decoration elements are not inherited
> from the parent's site.xml like <version>, <bannerRight>, <skin>, <links>.
> However, now the sub module's site properly outputs its own menu items (i.e.
> "Module-Item" instead of "Parent-Item" for the attached projects).
> This issues might be a duplicate/relative of MSITE-256 but as I cannot safely
> judge from its description, I opened a new issue.
--
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
