Thomas,
Actually, I think we can just modify those bin/zip assembly files to include
the NOTICE from the project, as is done in [TEXT]:
https://github.com/apache/commons-text/blob/5afc42360c077feb50f64dd702ca5b8a3b09c590/src/assembly/bin.xml#L25-L31
And then set an output directory in the assembly part for the maven shared
resources (I think that's coming from an older version of JCS that's somehow
referenced in the build?).
But changing those assembly files should give us the right release files.
Unfortunately I have no experience with reproducible builds in Maven, so
probably won't be of much help with the other thread.
-Bruno
On Thursday, 6 January 2022, 10:30:44 pm NZDT, Thomas Vandahl
<t...@apache.org> wrote:
Hi Bruno,
> Am 05.01.2022 um 21:59 schrieb Bruno P. Kinoshita
> <brunodepau...@yahoo.com.br.INVALID>:
>
> Did you have an old NOTICE file in the directory where you built the jcs
> release? I read the release instructions [1] and the code of
> commons-release-plugin [2], and found nothing that appeared to replace files
> or dates. The tag on GitHub is showing NOTICE.txt (with the extension) with
> the correct dates.
No, I haven’t. I completely rely on the files automatically generated by the
plugin. If you look at the code of the plugin, you see the mentioned
outputTimestamp property is being used.
I found docs about this here:
https://maven.apache.org/guides/mini/guide-reproducible-builds.html
> Maybe somebody else knows how that can happen.
The effective POM shows the following entry:
<project.build.outputTimestamp>2020-01-22T15:10:15Z</project.build.outputTimestamp>
Now we see why the year number in NOTICE is wrong. But who sets this?
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
