|
Forget the last comment, was doing something wrong To reproduce:
If you do a mvn site-deploy and look at the child it will have a ParentMenu which you don't want and it doen't have a ChildMenu which you do want. This is a very annoying one. In one of my multi-module projects, with 5 child projects I have to do: [at parent] mvn site site:deploy Each sub-project has its own unit and integration testsuites, and the sites include cobertura and findbugs reports, which make the process of deploying a site extremely slow. Duplicate of I have similar problems with 2.0-beta-6 and current 2.0-beta-7-SNAPSHOT from SVN (Revision: 657789). In 2.0-beta-5 the children's site.xml is respected, but in the other versions it is completely ignored: All menus defined in parent POM are shown in submodules (but should not). Furthermore, all other tags like bannerLeft and poweredBy are not overwritable in submodule's POM. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Another problem is that the content (dependencies) in the modules are wrong (I think they are from the parent).
Switching back to 2.0-beta-5 did resolve the issue, but at that version siteDirectory doens't work.