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 Le mardi 28 octobre 2014 20:05:12 Michael Osipov a écrit : > Hi, > > I'd like to fix MPIR-279 and by applying the logic from above. I am > having a hard time to find that spot which actually evalutes the snippet > above. > > Does someone know? > > Thanks, > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
