Re: [VOTE] Release Apache Log4j 2.26.1
"Piotr P. Karwasz" <[email protected]> Tue, 30 Jun 2026 08:38:12 +0200
| Newsgroups | gmane.comp.jakarta.log4j.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Gary, On 30.06.2026 01:58, Gary Gregory wrote: > Using: mvn verify -Prelease artifact:compare > -D'reference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1327' > > Fails for me but this is not a release requirement. You can try: CI=true mvn verify -Prelease,\!docker artifact:compare \ -D'reference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1327' There are three small bugs in the build, we should fix: 1. Upgrade mvnw, 2. Upgrade docker-maven-plugin, 3. Run CI build without `-Pjava8-tests,\!java8-incompat-fixes`, which is what setting CI=true does. The java8-tests profile moves jspecify from the `provided` to the `tests` scope to workaround a Java 8 reflection bug. This affects SBOM generation. Piotr