[
https://jira.codehaus.org/browse/MSITE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274959#comment-274959
]
Andreas Sewe commented on MSITE-582:
------------------------------------
What I meant by ??simply use the child's breadcrumbs wholesale whenever they
are a prefix to the parents?? is best explained using the example from the
e-mail mentioned above:
{quote}
<!--org.example:parent's site.xml -->
<breadcrumbs>
<item name="Example.org Site" href=http://example.org/"/>
<item name="Example.org Parent" href=http://example.org/parent/"/>
</breadcrumbs>
<!--org.example:site's site.xml -->
<breadcrumbs>
<item name="Example.org Site" href=http://example.org/"/>
</breadcrumbs>
{quote}
If building the site for {{org.example:site}} the plugin should realize that
the breadcrumbs entry of {{org.example:site}}'s {{site.xml}} doesn't add any
new breadcrumbs. This condition can then trigger special behaviour (hopefully
without breaking many existing sites).
The special behaviour I proposed was to simply take the *entire* breadcrumbs
entry of {{org.example:site}} (which we just found out to be subsumed by its
parent's breadcrumbs) and start over with just the iterms contained therein.
This is just a one possible way to handle this -- and perhaps not the best/most
flexible solution.
If you proposal also solves the use case in
<http://www.mail-archive.com/users@maven.apache.org/msg117974.html>, I am
perfectly happy with that. I think the most important thing (beyond solving use
cases) is to come up with a scheme that's easy to explain. Inheritence in Maven
is complicated enough already. :-(
> Make it possible to remove breadcrumbs in child projects again
> --------------------------------------------------------------
>
> Key: MSITE-582
> URL: https://jira.codehaus.org/browse/MSITE-582
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: New Feature
> Components: inheritance
> Affects Versions: 3.0
> Reporter: Andreas Sewe
> Attachments: example.tar.gz
>
>
> Currently a child can only add more breadcrumbs. There are situations,
> however, where it is desirable to remove some or all of the breadcrumbs
> defined by the parent, in particular when the Maven project hierarchy doesn't
> match the _natural_ hierarchy of the site. See
> <http://www.mail-archive.com/users@maven.apache.org/msg117974.html> for an
> example (also attached).
> One way to do this, without requiring changes to the {{site.xml}} format and
> with only minimal breakage of compatibility, would be to simply use the
> child's breadcrumbs wholesale whenever they are a prefix to the parents.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
