Hi folks,
We have fixed quite a few bugs and added some significant enhancements since
Apache Commons JCS 3.0 was released, so I would like to release Apache Commons
JCS 3.1.
Note that, although the core library of Log4j is an optional dependency to
commons-jcs, we have addressed CVE-2021-4422
> Am 03.01.2022 um 18:24 schrieb Thomas Vandahl :
>
> Hi folks,
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons JCS 3.0 was released, so I would like to release Apache
> Commons JCS 3.1.
>
> [X] +1 Release these artifacts
> [ ] +0 OK, but...
[x] +1 Release these artifacts
Build passed with no issues on my environment with `mvn clean test install site`
Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Maven home: /opt/apache-maven-3.8.2
Java version: 11.0.13, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Hi Bruno,
> Am 05.01.2022 um 06:41 schrieb Bruno P. Kinoshita
> :
>
> I didn't have much time, so inspected only one file, randomly selected, from
> the dist area. The src zip. @Thomas, I think the NOTICE has the date 2020? I
> think that can be fixed later? Everything else looks OK in that fi
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
cor
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
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
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
Hi folks,
could I please have one more PMC vote? If you think that the outputTimestamp
issue must be fixed before, then please vote -1 explicitly.
Bye, Thomas
> Am 03.01.2022 um 18:24 schrieb Thomas Vandahl :
>
> Hi folks,
>
> We have fixed quite a few bugs and added some significant enhance
Hello.
Le ven. 7 janv. 2022 à 19:49, Thomas Vandahl a écrit :
>
> Hi folks,
>
> could I please have one more PMC vote? If you think that the outputTimestamp
> issue must be fixed before, then please vote -1 explicitly.
>
> Bye, Thomas
>
> > Am 03.01.2022 um 18:24 schrieb Thomas Vandahl :
> >
> >
Hi Gilles,
> Am 14.01.2022 um 15:37 schrieb Gilles Sadowski :
>
>>> Maven artifacts are here:
>>>
>>> https://repository.apache.org/content/repositories/orgapachecommons-1576/org/apache/commons/commons-jcs3/3.1/
>
> I only see one ".pom" file and one ".xml" file (with their respective
> crypt
Hello.
Le lun. 17 janv. 2022 à 13:33, Thomas Vandahl a écrit :
>
> Hi Gilles,
>
> > Am 14.01.2022 um 15:37 schrieb Gilles Sadowski :
> >
> >>> Maven artifacts are here:
> >>>
> >>> https://repository.apache.org/content/repositories/orgapachecommons-1576/org/apache/commons/commons-jcs3/3.1/
> >
Hi Gilles,
> Am 17.01.2022 um 14:11 schrieb Gilles Sadowski :
>
> No; the remark is for making the reviewer's life easier, i.e just copy/paste
> the command and see the build succeed. Without the environment variable,
> the "javadoc" step fails IIRC.
Ok, thanks for the hint. I didn’t know this.
Hi Gilles,
> Am 17.01.2022 um 14:11 schrieb Gilles Sadowski :
>
> No; the remark is for making the reviewer's life easier, i.e just copy/paste
> the command and see the build succeed. Without the environment variable,
> the "javadoc" step fails IIRC.
Ok, thanks for the hint. I didn’t know this.
Hi folks,
> Am 03.01.2022 um 18:24 schrieb Thomas Vandahl :
>
> Please review the release candidate and vote.
This vote passes with the following votes:
Gilles Sadowski: +1
Bruno Kinoshita: +1
Thomas Vandahl: +1
I’ll go ahead with the release publication.
Thanks to the voters.
Bye, Thomas
Would it be worth starting with a list of commit one liners then release
manager (or whom even) edits for more readability?
Is a ticket to track resolution of the time issue needed if not already raised
to ensure this does get resolved at some point in the future whether it be
environment or bu
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-
17 matches
Mail list logo
