Am 2014-10-29 um 02:39 schrieb Hervé BOUTEMY:
see doxia-integration-tools DefaultSiteTool populateParentMenu(...) [1] and
populateModulesMenu(...) [2] called by getDecorationModel(...)
then getDecorationModel(...) is called from
AbstractSiteRenderingMojo.createSiteRenderingContext(...)
But looking at MPIR-279, I fear you're fighting against a non-bug, just some
unexpected consequences of not using the standard directory layout from
modules (ie directory = artifactId) without manually updating a serie of POM
elements which are calculated with the convention
Perhaps what can help is documenting "what POM elements to be manually defined
in case of non-standard module directory path": I never tried to do so, always
fighting about what was told as "a bug"
Regards,
Hervé
[1]
http://maven.apache.org/doxia/doxia-tools/doxia-integration-tools/xref/org/apache/maven/doxia/tools/DefaultSiteTool.html#L638
[2]
http://maven.apache.org/doxia/doxia-tools/doxia-integration-tools/xref/org/apache/maven/doxia/tools/DefaultSiteTool.html#L733
Salut Hervé,
the code snippets look like the stuff I was looking for. I don't think
that MPIR-279 follows some non-default layout therefore I have marked
two issues as duplicates. I ran into this issue at work, so I have a
bigger project to test with.
I'll take a look at some demo code in the next couple of days.
Thanks for the pointers,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
