Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

2022-01-06 Thread Bruno P. Kinoshita
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 asse

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

2022-01-06 Thread Bruno P. Kinoshita
Hi Thomas, Saw your other thread about the reproducible builds. Really interesting. I found something else, pertinent to this thread, so posting it here. I was dumbfound with that 2020, so I opened both the NOTICE.txt from the GitHub tag, and the one from the zip bin dist archive, one on each

[all] project.build.outputTimestamp set in org.apache:apache, was Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

2022-01-06 Thread Thomas Vandahl
Hi folks, This may be of general interest, at least I had no idea about the consequences. So I thought I’d share the result of my research. > Am 06.01.2022 um 10:30 schrieb Thomas Vandahl : > >> Maybe somebody else knows how that can happen. > The effective POM shows the following entry: > 2020-

Re: [VOTE] Release Apache Commons JCS 3.1 based on rc2

2022-01-06 Thread Thomas Vandahl
Hi Bruno, > Am 05.01.2022 um 21:59 schrieb Bruno P. Kinoshita > : > > 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 dat