Due to a problem found in testing this release vote is cancelled.
> On Dec 8, 2021, at 1:42 AM, Volkan Yazıcı wrote:
>
> +1
>
> `verify` keeps failing due to SimplePerfTest failures – I will rely on CI
> and others for this.
> I have tested a custom JTL template, the killer feature of this JTL
+1
`verify` keeps failing due to SimplePerfTest failures – I will rely on CI
and others for this.
I have tested a custom JTL template, the killer feature of this JTL
release, it works.
On Tue, Dec 7, 2021 at 5:12 AM Ralph Goers
wrote:
> This is a vote to release Log4j 2.15.0, the next version o
Java 7 is no longer required. Most of the build requires Java 8. The modules
with java9 in their names require and version from Java 9 up. For some reason
log4j-perf says it requires Java 11. I have no idea why.
Ralph
> On Dec 7, 2021, at 3:48 PM, Ron Grabowski
> wrote:
>
> I built with Jav
Java 7 was only used in older releases. Java 9 can be replaced with 11 as
there’s a module that requires 11.
Matt Sicker
> On Dec 7, 2021, at 16:49, Ron Grabowski
> wrote:
>
> I built with Java 8 because that's the default JDK on this Windows 10 box.
> Based on https://logging.apache.org/
I built with Java 8 because that's the default JDK on this Windows 10 box.
Based on https://logging.apache.org/log4j/2.x/build.html I understand why Java
9 is needed. Why are Java 7 and Java 11 JDKs required to build? It took a few
minutes to find a JDK 7 installer. I had to add a new toolchai
+1
Building
- mvn clean install
- mvn apache-rat:check
- mvn revapi:check -pl log4j-api
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: /usr/local/Cellar/maven/3.8.4/libexec
Java version: 1.8.0_292, vendor: AdoptOpenJDK, runtime:
/Library/Java/JavaVirtualMachines/adoptop
Gotcha.
On Tue, Dec 7, 2021 at 3:27 PM Matt Sicker wrote:
> Run maven using Java 8. The build doesn’t specify requirements on that, so
> the default JDK is used, not a specific toolchain entry.
>
> Matt Sicker
>
> > On Dec 7, 2021, at 14:25, Gary Gregory wrote:
> >
> > Hi Matt:
> >
> > When I
Run maven using Java 8. The build doesn’t specify requirements on that, so the
default JDK is used, not a specific toolchain entry.
Matt Sicker
> On Dec 7, 2021, at 14:25, Gary Gregory wrote:
>
> Hi Matt:
>
> When I run 'mvn clean install' on Java 11 I get:
>
> [ERROR] Failed to execute goa
Hi Matt:
When I run 'mvn clean install' on Java 11 I get:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile
(default-testCompile) on project log4j-api: Compilation failure
[ERROR]
/Users/garydgregory/temp/rc/logging-log4j2/log4j-api/src/test/java/org/
+1
rat: success
mvn install: success (no flakes)
$ mvn -v
Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 1.8.0_282, vendor: Azul Systems, Inc., runtime:
/home/ckozak/.tools/jdk/zulu8.52.0.23-ca-jdk8.0.282-linux_x64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linu
+1
Signatures good, tests pass, etc. Environment (mixed toolchain depending on
which module is being tested):
openjdk version "1.8.0_312"
OpenJDK Runtime Environment (Zulu 8.58.0.13-CA-macos-aarch64) (build
1.8.0_312-b07)
OpenJDK 64-Bit Server VM (Zulu 8.58.0.13-CA-macos-aarch64) (build 25.312-
This is a vote to release Log4j 2.15.0, the next version of the Log4j 2 project.
Please download, test, and cast your votes on the log4j developers list.
[] +1, release the artifacts
[] -1, don't release because...
The vote will remain open for 72 hours (or more if required). All votes are
welco
12 matches
Mail list logo
