Fixed (and tested!) this in `logging-parent` to use `project.build.outputTimestamp` instead. Since distribution code is shipped by `logging-parent`, we will do a `logging-parent` version `10.1.1` release first. Consequently issue an RC2 for `-tools` version `0.5.0`.
On Sun, Oct 1, 2023 at 4:50 PM Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > Hi Gary, > > On Sun, 1 Oct 2023 at 14:20, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > [Note to reviewers: You MUST review a src package, not a git tag.] > > > > -1: Failure running 'mvn clean verify' > > Nice catch. > > The problem comes from the modification date of each file in the > source archive (i.e. start of the epoch). > In this case the Maven Resources Plugin fails to copy > `src/main/resources/log4j-changelog.xsd` to > `target/classes/log4j-changelog.xsd`, because the source modification > date is 0, while the destination modification date is 0 (the file does > not exist). > Granted that this seems like a bug in the Maven Resources Plugin, but > we should fix the modification dates in the archive. > > I am also voting -1. > > Piotr >
