I think this should be fixed with the latest logging-parent pom. The timestamp of the build is set at the time of release so that subsequent builds of that tag still end up with the same output timestamp.
On Sat, Jan 8, 2022 at 12:37 PM Gary Gregory <[email protected]> wrote: > > Is this a side effect of the reproducible build change to the POM? Is > sounds like we need to set the end year of the Javadoc plugin explicitly. > > Gary > > On Sat, Jan 8, 2022, 13:26 Matt Sicker <[email protected]> wrote: > > > Well that looks like a time stamp of 0 or so with a time zone offset. > > > > — > > Matt Sicker > > > > > On Jan 8, 2022, at 04:52, Gary Gregory <[email protected]> wrote: > > > > > > Our Javadoc say "Copyright © 1999-1969 ..." on > > > https://logging.apache.org/log4j/2.x/log4j-api/apidocs/index.html > > > > > > Gary > >
