That you avoid it, does not mean that everyone does. It also is not about the parent POM, but the parent site.xml forced upon me. A POM is never a problem, because everything from a POM can be overridden in consuming projects. My question focuses on ways to override things I do not like in site.xml, a case which can also occur within projects of the same organisation. I am still confident that there is a way to override or undefine what I do not need from the site.xml, which is why I asked here. If you do not know, you can just say so. Thanks for your advice to copy things from the parent POM and site I like, I did that already days ago. But it is not what I want, because 99% of the defaults are OK for me. I would not have asked, if this DRY violation would not bug me so much.
-- Alexander Kriegisch https://scrum-master.de Jörg Schaible schrieb am 07.02.2024 01:24 (GMT +07:00): > 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
