Hi Alexander, On Tuesday, 6. February 2024, 02:18:36 CET Alexander Kriegisch wrote: > 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.
OK, this is something I absolutely avoid. Typically I have a standalone parent for the company/entity/whatever that can be used for all projects sharing global stuff like emails, SCM URLs, URLs for distributions sites, versions, etc. And it is a great place for profile definitions with preconfigured plugins to build all kind of artifact types relevant for your entity. > I am consuming it, because I like the defaults for plugin > and dependency versions and configurations. If I really need something, I copy it over and adjust it to our naming conventions. Always keep control of your own build. I know that projects like spring-boot give a different advice, but typically you're then left alone with all the other configuration stuff. Then you will have to add entries to your own POMs everywhere e.g. for deployment, distribution, etc. and cannot use properties for the shared stuff like domains in emails, all kind of URLs. Maintenance is getting harder, if something of this changes. > 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. No help for this case, sorry. Regards, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
