On 2024/02/28 14:01:42 sebb wrote: > On Wed, 28 Feb 2024 at 13:40, Michael Osipov <micha...@apache.org> wrote: > > > > On 2024/02/22 06:59:01 Alexander Kriegisch wrote: > > > Hello Maven community. > > > > > > When generating Maven sites, I like to keep the diffs to previous > > > version to the absolute minimum before committing changes to a published > > > site. My commits should only contain content changes. Therefore, I > > > already use this in my site.xml: > > > > > > <custom> > > > <fluidoSkin> > > > <skipGenerationDate>true</skipGenerationDate> > > > </fluidoSkin> > > > </custom> > > > > > > Unfortunately, I found no way to suppress these generated tags on each > > > single page: > > > > > > <meta name="generator" content="Apache Maven Doxia Site Renderer > > > 1.11.1" /> > > > <meta name="date" content="2024-02-22 13:52:19 +0700" /> > > > > > > They constitute about 90% of my commit diffs, making it look like all > > > pages have changed in the commit log, even though maybe I just fixed a > > > typo on a single page. How can I customise that behaviour? > > > > I do not fully understand which problem you have. As long as you stay on > > the same version of all affected components there should be no diff, but > > only your content change. Can you elaborate? What do you exactly change? > > Suppose you release version 1.2.2 of a project using Doxia 1.11.0 > Later you would like to release version 1.2.3, by then Doxia 1.11.1 is out. > > As part of checking the release, you would like to check that the > Javadoc changes properly reflect the code changes. > However the Doxia version change generates tons of spurious output.
True, that is what I wanted to hear. I have/had the same problem during dev/testing. Raise an issue with the skin, please. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
