I was able to build on Windows 10, with Zulu Java 6.
On Tue, Dec 21, 2021 at 1:29 PM Remko Popma wrote:
> +1 I am changing my vote.
> My earlier pipecleaning program failed because the config had a JmsAppender
> configured in it... My bad.
> Signatures are good.
> Pipecleaning program works on J
+1 I am changing my vote.
My earlier pipecleaning program failed because the config had a JmsAppender
configured in it... My bad.
Signatures are good.
Pipecleaning program works on Java 6 when I remove the JmsAppender from the
config.
On Wed, Dec 22, 2021 at 6:23 AM Ralph Goers
wrote:
> My +1
>
My +1
I tested it in an Ubuntu VM and verified it with Java 6.
Ralph
> On Dec 20, 2021, at 10:18 PM, Ralph Goers wrote:
>
> This is a vote to release Log4j 2.3.1, a security release for Java 6 users.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release
+1
rat and build succeed, however I don't have a jre6 around to test with.
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
+1
Signatures good, build good, artifacts good.
--
Matt Sicker
> On Dec 20, 2021, at 23:18, Ralph Goers wrote:
>
> This is a vote to release Log4j 2.3.1, a security release for Java 6 users.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artif
+1
I did the same steps as Rob but I only used Java 8:
- mvn apache-rat:check -DskipTests
- mvn clean install
- mvn site -DskipTests
openjdk version "1.8.0_312"
OpenJDK Runtime Environment (build 1.8.0_312-bre_2021_10_20_23_15-b00)
OpenJDK 64-Bit Server VM (build 25.312-b00, mixed mode)
Apache M
+1
I wrote a simple HelloWorld app with 2.3.1 running on jdk1.6.0_45 to
further verfiy LOG4J2-3198. These commands ran successfully too:
mvn clean install
mvn site -DskipTests
mvn apache-rat:check -DskipTests
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: C:\project
You should try 2.3. I bet you get the same result. I bet we enhanced the plugin
system to ignore plugins that get NoClassDefFoundError.
Ralph
> On Dec 21, 2021, at 6:41 AM, Remko Popma wrote:
>
> Gary,
>
> No it’s literally that pipe cleaning class, the api and core jar, and a
> Log4j2.xml w
Gary,
No it’s literally that pipe cleaning class, the api and core jar, and a
Log4j2.xml with just the console Appender.
That should work though without any extra dependencies.
Interestingly the same setup does work without errors with 2.12.3 on Java 7.
What’s the difference between 2.3.1 a
Remko:
JMS is not built-in the JRE, do you have JMS in your configuration for
this test? If you do, then you'd need the JMS API and a provider as
dependencies.
Gary
On Tue, Dec 21, 2021 at 7:37 AM Ralph Goers wrote:
>
> Hmmm. This is not what I was expecting. If it didn’t work I would have
> e
Hmmm. This is not what I was expecting. If it didn’t work I would have expected
bad class version exceptions.
Ralph
> On Dec 21, 2021, at 4:28 AM, Remko Popma wrote:
>
> -1 it does not work...
>
> Problem running a simple pipecleaning test on Java 6 with 2.3.1...
> My pipecleaning program is
-1 it does not work...
Problem running a simple pipecleaning test on Java 6 with 2.3.1...
My pipecleaning program is something simple like this
public class Pipecleaning {
public static void main(String[] args) {
org.apache.logging.log4j.LogManager.getLogger().info("HELLO
USER ${sys:u
12 matches
Mail list logo
