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"
I did a code analysis now. At first glace, the SiteTool code is exactly
what I need to adapt. The problem lays in the ModulesReport. It should
be an exact copy of ref="modules"/SiteTool behavior. I'll try a patch to
report to the watches, additionally, I'll try to create a IT for that.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
