[
http://jira.codehaus.org/browse/MSITE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251023#action_251023
]
Brett Porter commented on MSITE-502:
------------------------------------
I think at the time I implemented that, I had a different perception on how the
inheritance would be used. If you were referring to a parent, you might be
establishing a permanent link to a top level project that might otherwise be
hard to obtain.
I'm not sure if anyone has come to depend on that behaviour, but I haven't seen
it widely used myself. Perhaps you could deprecate those expressions and offer
better replacement tags in the site descriptor that are more descriptive of the
intent (e.g. since they are no longer expressions, you could even indicate in
the descriptor whether to interpolate them or not).
> Multiple Parent-Links and additional module-link inherited wrong from parent
> ----------------------------------------------------------------------------
>
> Key: MSITE-502
> URL: http://jira.codehaus.org/browse/MSITE-502
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: inheritance, multi module, site descriptor
> Affects Versions: 2.1.1
> Reporter: Michael Wenig
> Fix For: 2.3
>
> Attachments: siteInheritance.zip
>
>
> Attached is a couple of projects showing a problem with the site inheritance.
> The projects have the following structure:
> parentPom1
> -> projectA (parentPom2, with a submodule 'dummyModule' and attached site.xml)
> -> projectB (parentPom3)
> -> projectC (projectRoot with a submodule 'projectModule')
> I ran the following commands:
> parentPom1: install
> projectA: site site:attach-descriptor install
> projectB site install
> projectC site install
> I added the corresponding target-folders to the zip:
> projectA:
> generated correctly
> projectB:
> shows two(!) parent links:
> -> to parentPom1 (which is wrong and IMHO inherited out of the attached
> site-descriptor)
> -> to parentPom2 (which is correct)
> projectC (root):
> shows two(!) parent links:
> -> to parentPom1 (which is wrong and IMHO inherited out of the attached
> site-descriptor)
> -> to projectB (which is correct)
> shows two modules:
> -> dummyModule (the one of projectA which is wrong and IMHO inherited out of
> the attached site-descriptor)
> -> projectModule (correct)
> ==> I expected the parent-Menu to only contain the direct parent
> ==> I expected the modules menu to only contain modules of the pom and not
> the modules of a parent...
> Content of the attached site descriptor:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?><project
> xsi:schemaLocation="http://maven.apache.org/DECORATION/1.0.1
> http://maven.apache.org/xsd/decoration-1.0.1.xsd";
> xmlns="http://maven.apache.org/DECORATION/1.0.1";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> <body>
> <menu name="Parent Project" inherit="top" ref="parent">
> <item name="parentPom1" href="..\index.html" />
> </menu>
> <menu name="Modules" inherit="bottom" ref="modules">
> <item name="dummyModule" href="projectA1/index.html" />
> </menu>
> <menu inherit="bottom" ref="reports" />
> </body>
> </project>
> {code}
> I think the problem are the contained item-tags which are included in the
> sites of consumer projects.
--
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
