Thanks Jörg, but that does not answer my question. I do not want to generate a site for the parent. I am talking about the module using the parent POM. BTW, the parent POM is not even under my control, it is from another organisation. I am consuming it, because I like the defaults for plugin and dependency versions and configurations. Only the site.xml annoys me. I do not want their menu structure and logo in my app's Maven site. The problem is, as I described: I do not know how to use the parent POM without also being forced to use the paren site.xml, which is attached to the artifact. This inheritance is nice, but I need a way to avoid, override or overrule it and make Maven Site Plugin use my own site.xml exclusively.
-- Alexander Kriegisch https://scrum-master.de Jörg Schaible schrieb am 06.02.2024 05:04 (GMT +07:00): > Hi Alexander, > > On Monday, 5. February 2024, 05:36:35 schrieb Alexander Kriegisch wrote: >> Neither in [1] nor in [2] I can find a way to completely disregard or >> override a site.xml from the parent POM. I want to inherit a lot from a >> specific parent POM, such as dependency management and properties, but not >> the site.xml. Is there a way to do that? >> >> E.g., [2] seems to imply that if I define my own breadcrumbs, they override >> the parent's ones, but that is not true. I also cannot eliminate the >> bannerLeft from the parent, only override it. But I do not want any banner >> at all. Sorry for asking a maybe simple-minded question like this, but for >> the life of me, I cannot find the solution using web search, documentation >> or trial & error. >> >> [1] >> https://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor. >> html [2] >> https://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.htm >> l > > You can achieve a separate site generation for the parent only by using a > profile and an own site directory: > > 1/ use src/site-parent in the parent pom's project for its site content > 2/ define a profile that us automatically activated id the directory src/site- > parent exists > 3/ configure the site plugin's siteDirectory parameter to use src/site-parent > > The trick is that the profile is automatically enabled, when you build the > parent project, but it is never active in any other project, since none has > an > existing src/site-parent directory. > > Regards, > Jörg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
