JDK 9 Developer Preview is now available on java.net

Hi Nick, *JDK 9 Developer Preview is now available on java.net [1] * Developer Preview milestone: - A reasonably stable build suitable for broad testing by the developer community is available. JDK 9 Builds 163 and higher include all planned features. *Attention annotation

Re: Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #51

These windows jenkins builds don't seem super stable anyways. Not many apache projects are using them, so it could be environmental. On 7 April 2017 at 19:24, Gary Gregory wrote: > Note that I ran a full build before this commit (mvn clean install) and it > worked. > >

Fwd: Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #51

Note that I ran a full build before this commit (mvn clean install) and it worked. Gary -- Forwarded message -- From: Apache Jenkins Server Date: Fri, Apr 7, 2017 at 5:08 PM Subject: Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited

[jira] [Created] (LOG4J2-1868) Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0

Gary Gregory created LOG4J2-1868: Summary: Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0 Key: LOG4J2-1868 URL: https://issues.apache.org/jira/browse/LOG4J2-1868 Project: Log4j 2 Issue Type:

[jira] [Created] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0

Gary Gregory created LOG4J2-1869: Summary: Update Kafka client from 0.10.1.1 to 0.10.2.0 Key: LOG4J2-1869 URL: https://issues.apache.org/jira/browse/LOG4J2-1869 Project: Log4j 2 Issue Type:

Weird compilation error

Hi All: I'm seeing this in master: [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @ log4j-1.2-api --- [INFO] [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ log4j-1.2-api --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 71

Re: Weird compilation error

Could be I'm going to run the build with each ActiveMQ release since what we have and see what happens. I'll nuke the latest one I have just in case it's junked. Gary On Fri, Apr 7, 2017 at 1:49 PM, Matt Sicker wrote: > Corrupted downloads perhaps? That's very odd! > > On 7

Re: Weird compilation error

I added to log4j-1.2-api: org.apache.logging.log4j log4j-core test test but that blows up Maven 3.3.9: [ERROR] [ERROR] Some problems were encountered while processing the POMs: [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be

Jenkins build is back to normal : Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #52

See - To unsubscribe, e-mail:

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #51

See Changes: [ggregory] Upadate Apache Active MQ from 5.14.1 to 5.14.2 for testing. --

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #51

See Changes: [ggregory] Upadate Apache Active MQ from 5.14.1 to 5.14.2 for testing. --

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #53

See Changes: [garydgregory] Upadate Apache Active MQ from 5.14.3 to 5.14.4 for testing.

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #52

See Changes: [garydgregory] Upadate Apache Active MQ from 5.14.2 to 5.14.3 for testing.

Re: Yet another logging facade

I just took a look at the list. I don’t see the response that points to bugzilla. In your comment you mentioned that Log4j provides an api but you didn’t list the reasons why it is better. Remko posted a stack overflow post that has 10 reasons why it is better. But more importantly, users

Re: Yet another logging facade

See http://stackoverflow.com/questions/41633278/can-we-use-all-features-of-log4j2-if-we-use-it-along-with-slf4j-api/41635246#41635246 . Note that item 10 on this

Re: Yet another logging facade

I got a response on the mailing list. There's a public bugzilla we can comment on apparently which is linked in the PDF. On 6 April 2017 at 20:02, Matt Sicker wrote: > I'm not sure where they develop the standards, but there's an osgi-dev > mailing list (where I found this

Re: [qos.ch-announce] Release of SLF4J version 1.8.0-alpha0

We will have to modify log4j-slf4j-impl to support the new binding mechanism. I know it uses service loader but I haven’t looked at the details. I looked at service loader when I created the binding between our api and core but decided not to use it because I wanted to also include the logic to

Fwd: [qos.ch-announce] Release of SLF4J version 1.8.0-alpha0

So how shall we go about handling this? -- Forwarded message -- From: QOS.ch annoucements Date: 7 April 2017 at 05:46 Subject: [qos.ch-announce] Release of SLF4J version 1.8.0-alpha0 To: annou...@qos.ch Java 9 modularization = I am

Re: Weird compilation error

Does it have a dependency on log4j-core:test? It should. Could be a bug in your beta version of Maven ;) On 7 April 2017 at 14:46, Gary Gregory wrote: > Hi All: > > I'm seeing this in master: > > [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @ log4j-1.2-api >

Re: Weird compilation error

Corrupted downloads perhaps? That's very odd! On 7 April 2017 at 15:48, Gary Gregory wrote: > Hm, > > I had changed active mq testing from 5.14.1 to 5.14.4 and that yields: > > [ERROR] error: error reading C:\Users\ggregory\.m2\repository\org\apache\ >

Re: Weird compilation error

Maybe it's because it's a new snapshot version and you need to run "mvn install" at least once? On 7 April 2017 at 15:40, Matt Sicker wrote: > This is the first I've ever seen that error, and it's not popping up in > Jenkins or anything. I don't think the code has changed

Re: Weird compilation error

This is the first I've ever seen that error, and it's not popping up in Jenkins or anything. I don't think the code has changed since 2.8.2, so I don't know why it would break. On 7 April 2017 at 15:34, Gary Gregory wrote: > This is with Maven 3.3.9 though. > > Gary > >

Re: Weird compilation error

It's already in the pom: https://github.com/apache/logging-log4j2/blob/master/log4j-1.2-api/pom.xml#L74 I don't think it's scope=test, but type=test-jar. On 7 April 2017 at 15:41, Gary Gregory wrote: > I added to log4j-1.2-api: > > > org.apache.logging.log4j

Re: Weird compilation error

Hm, I had changed active mq testing from 5.14.1 to 5.14.4 and that yields: [ERROR] error: error reading C:\Users\ggregory\.m2\repository\org\apache\activemq\activemq-broker\5.14.4\activemq-broker-5.14.4.jar; invalid LOC header (bad signature) [ERROR] error: error reading

Re: Weird compilation error

This is with Maven 3.3.9 though. Gary On Fri, Apr 7, 2017 at 1:11 PM, Matt Sicker wrote: > Does it have a dependency on log4j-core:test? It should. Could be a bug in > your beta version of Maven ;) > > On 7 April 2017 at 14:46, Gary Gregory wrote: >