Re: Logger names for nested classes

Rather than implementing this I would rather have the separator chars be specifiable in the configuration. Blatantly making this change might cause compatibility problems, although I am not really sure how it could. Ralph > On Aug 12, 2017, at 11:29 AM, Gary Gregory wrote: > > Hi All, > > I

Re: Logger names for nested classes

., "Gary Gregory" >>> wrote: >>>>> >>>>> You are talking about replacing $ with dot in the getLogger(Class) >> API? >>>>> >>>>> Gary >>>>> >>>>>> On Aug 13, 2017 01:57, "Dominik P

Log4j 2.9

I’d like to start the release process next weekend for Log4j 2.9. I believe there is some web site work that has to take place for that to happen to integrate with the new Scala release. Has Scala been published to the web site? I can’t find it in SVN. Ralph

Re: Log4j 2.9

ld get that integrated > first. I'm not exactly sure where the links should go in the 2.9 version of > the site as they're no longer components of the release. > > On 14 August 2017 at 00:39, Ralph Goers wrote: > >> I’d like to start the release process next weekend fo

Re: Logger names for nested classes

> On Aug 14, 2017, at 11:49 AM, Gary Gregory wrote: > > On Mon, Aug 14, 2017 at 12:35 PM, Gary Gregory > wrote: > >> Probably for Ralph: >> >> Right now, it's the LogManager in log4j-api that converts Class names into >> Logger names. >> >> There is no getLogger(Class) API in the Core Logger

Re: Logger names for nested classes

> On Aug 14, 2017, at 1:38 PM, Gary Gregory wrote: > > On Mon, Aug 14, 2017 at 2:08 PM, Ralph Goers <mailto:ralph.go...@dslextreme.com>> > wrote: > >> >>> On Aug 14, 2017, at 11:49 AM, Gary Gregory >> wrote: >>> >>

Re: Jenkins build became unstable: Log4j 2.x #2980

I don’t recall having seen this error before. Did the latest commit break something? Ralph > On Aug 14, 2017, at 1:12 PM, Apache Jenkins Server > wrote: > > See > > >

Re: Logger names for nested classes

$ but only >>> use >>>>> "."s. >>>>> >>>>> Gary >>>>> >>>>> On Mon, Aug 14, 2017 at 3:07 PM, Matt Sicker >> wrote: >>>>> >>>>>> The logger name hierarchy interpreta

Re: Logger names for nested classes

or this > hierarchySeparators="./$" ... Is my understanding correct? >> >> >> On Sun, Aug 20, 2017 at 3:47 AM, Ralph Goers >> wrote: >> >>> I agree. >>> >>> Ralph >>> >>>> On Aug 19, 2017, at 11

Scala web site

The Scala web site is now published at http://logging.apache.org/log4j/scala/index.html . I have modified it to use the generic Log4j 2 logo instead of the one for Log4j 2 2.7. I see 3 options for linking to the site: 1. Add a link to the Log4j

Re: Build failed in Jenkins: Log4j 2.x #3005

I don’t understand why this is failing. My local machine is running build 174. Was ProcessHandle.pid() really added that late? Ralph > On Aug 20, 2017, at 7:51 PM, Apache Jenkins Server > wrote: > > See > > > Cha

Re: Build failed in Jenkins: Log4j 2.x #3013

I have posted to infra to try to find out how to determine what the Java home path needs to be. However, my experience is that questions posted to the infra list never get answered so I may have to create a Jira issue. Ralph > On Aug 21, 2017, at 8:33 AM, Apache Jenkins Server > wrote: > >

Jenkins JDKs

For future reference - https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix Ralph

Re: org.apache.logging.log4j.core.LoggerContext getLogger(Class)

Did you ask this question last week? Why is it needed? Why can’t this be handled in LogManager? Ralph > On Aug 21, 2017, at 2:10 PM, Gary Gregory wrote: > > Hi All: > > I have a need for the shortcut method > org.apache.logging.log4j.core.LoggerContext getLogger(Class) which would > use getC

Re: org.apache.logging.log4j.core.LoggerContext getLogger(Class)

of the > LogManager classes (only in a few rare places.) > > Gary > > On Mon, Aug 21, 2017 at 3:47 PM, Ralph Goers > wrote: > >> Did you ask this question last week? Why is it needed? Why can’t this be >> handled in LogManager? >> >> Ralph >

Re: [log4j2] sys props driving me nuts

I plan on starting the 2.9 release any day… Ralph > On Aug 21, 2017, at 3:25 PM, Gary Gregory wrote: > > On Thu, Jul 20, 2017 at 9:05 PM, Gary Gregory > wrote: > >> On Thu, Jul 20, 2017 at 7:19 PM, Matt Sicker wrote: >> >>> I haven't been able to get to this so far this week. Been finishing

Re: org.apache.logging.log4j.core.LoggerContext getLogger(Class)

de. > > Gary > > On Mon, Aug 21, 2017 at 4:30 PM, Ralph Goers > wrote: > >> So you are saying that your application is getting Loggers by doing >> LoggerContext.getLogger()? I guess I don’t really understand why that is a >> good idea. Are you saying yo

Re: org.apache.logging.log4j.core.LoggerContext getLogger(Class)

I am against encouraging users to directly acquire a Logger. Ralph > On Aug 21, 2017, at 5:24 PM, Gary Gregory wrote: > > On Mon, Aug 21, 2017 at 6:01 PM, Ralph Goers > wrote: > >> It is actually funny that you say that. The API we provide for performing >> logg

Re: org.apache.logging.log4j.core.LoggerContext getLogger(Class)

17, at 6:45 PM, Gary Gregory wrote: > > Hi Ralph, > > Would you say that is your opinion or the intent of the design? And if the > latter, should we adjust the Javadoc accordingly. > > Gary > > On Mon, Aug 21, 2017 at 7:31 PM, Ralph Goers > wrote: > >>

Re: org.apache.logging.log4j.core.LoggerContext getLogger(Class)

ses of "get me a logger" even though it is in the > log4j-api module? > > Thank you again! > Gary > > > On Mon, Aug 21, 2017 at 10:34 PM, Gary Gregory > wrote: > >> On Mon, Aug 21, 2017 at 10:27 PM, Ralph Goers >> wrote: >> >>> I

Re: Scala web site

I have already added the link to the Log4j site.xml so it will be there when I do the release. Modifying the main site should be pretty easy to do. Ralph > On Aug 24, 2017, at 1:05 PM, Mikael Ståldal wrote: > > 3. Do both seems fine to me. > > > On 2017-08-20 20:08,

Re: [log4j2] sys props driving me nuts

that. >>>> >>>> On 21 August 2017 at 17:43, Gary Gregory >> wrote: >>>> >>>>> Sweet. I've been going through the back log and picking some >> low-hanging >>>>> fruit as you may have noticed. Maybe others could d

Re: [log4j2] sys props driving me nuts

Scratch that. It seems Log4j now has a dependency on log4j-server? That must be released before a release build can be run. Why does the main project have a dependency on that? Ralph > On Aug 26, 2017, at 11:21 AM, Ralph Goers wrote: > > > I am just about to start the release

Re: [log4j2] sys props driving me nuts

I moved the test classes that were dependent on log4j-server to that project. Ralph > On Aug 26, 2017, at 11:27 AM, Ralph Goers wrote: > > Scratch that. It seems Log4j now has a dependency on log4j-server? That must > be released before a release build can be run. Why does the

Re: [log4j2] sys props driving me nuts

at 14:14, Gary Gregory wrote: > >> IMO, the simplest solution is to bring log4j-server back into the main >> repo. >> >> Gary >> >> On Aug 26, 2017 12:27, "Ralph Goers" wrote: >> >>> Scratch that. It seems Log4j now has a dependency

Release build failed

The release build failed with something I have never seen before. I am going to try a normal build and see if it works. Ralph [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on project log4j-core: There are test failures. [INFO] [E

Re: Release build failed

t. Strange. >> >> On 26 August 2017 at 14:45, Ralph Goers >> wrote: >> >>> The release build failed with something I have never seen before. I am >>> going to try a normal build and see if it works. >>> >>> Ralph >>> >>

Re: Release build failed

The release build ran fine the second time around. Now I have to verify it, build the site, etc. Ralph > On Aug 26, 2017, at 1:20 PM, Ralph Goers wrote: > > The regular build ran fine. I’m trying it again. > > Ralph > >> On Aug 26, 2017, at 1:18 PM, Gary Gregory

Re: Release build failed

I’d prefer not to add enhancements until after the release vote. Ralph > On Aug 26, 2017, at 1:58 PM, Matt Sicker wrote: > > Sounds good. Do you want me to hold off on merging the LOG4J2-1431 branch? > > On 26 August 2017 at 15:57, Ralph Goers wrote: > >> The re

[VOTE] Release Log4j 2.9.0-rc1

This is a vote to release Log4j 2.9.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 welcome

Re: [VOTE] Release Log4j 2.9.0-rc1

Matt added an exclude for the docker file back before the 2.8. release. I’m not sure why. Ralph > On Aug 27, 2017, at 7:50 AM, Gary Gregory wrote: > > Minor bug but not a blocker: the Dockerfile is missing from the src > distribution zip. > > Gary > > On Sat, Aug 26

Re: [VOTE] Release Log4j 2.9.0-rc1

INFO] > > > > Thoughts? Since CLIRR is dead, we could also switch to japicmp. > > Gary > > > > > On Sat, Aug 26, 2017 at 8:45 PM, Ralph Goers > wrote: > >> This is a vote t

Re: [VOTE] Release Log4j 2.9.0-rc1

>. Ralph > On Aug 27, 2017, at 6:41 AM, Gary Gregory wrote: > > Link to KEYS file please? > > Gary > > On Sat, Aug 26, 2017 at 8:45 PM, Ralph Goers > wrote: > >> This is a vote to release Log4j 2.9.0 the next version of the Log4j 2 >> project. &

Re: [VOTE] Release Log4j 2.9.0-rc1

i%22 >> >> On 28 August 2017 at 10:17, Gary Gregory wrote: >> >>> It sorts pertier? >>> >>> On Mon, Aug 28, 2017 at 9:15 AM, Matt Sicker wrote: >>> >>>> Any particular reason this is tagged as 2.9.0 instead of 2.9

Re: [VOTE] Release Log4j 2.9.0-rc1

28 August 2017 at 10:17, Gary Gregory wrote: >> >>> It sorts pertier? >>> >>> On Mon, Aug 28, 2017 at 9:15 AM, Matt Sicker wrote: >>> >>>> Any particular reason this is tagged as 2.9.0 instead of 2.9? >>>> >>>> On

Re: [VOTE] Release Log4j 2.9.0-rc1

Here is my +1 Ralph > On Aug 26, 2017, at 7:45 PM, Ralph Goers wrote: > > This is a vote to release Log4j 2.9.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,

[VOTE][RESULT] Log4j 2.9.0-rc1

The vote to release Log4j 2.9.0 based on release candidate 1 has passed with +1 votes from Gary Gregory, Matt Sicker, Mikael Ståldal, Remko Popma, and Ralph Goers. No other votes were cast. I will continue with the release process. Ralph

Re: Module log4j-core-its not in MC

Yes, I manually deleted that before publishing to central. I can’t think of any reason why anyone would need that as a dependency. The release process used to manually delete several other modules but I modified the poms to have the deploy goal be ignored. Apparently I missed core-its. That will

Re: Module log4j-core-its not in MC

We publish unit test jars. Those contain test classes with some value for testing end user applications. Ralph > On Aug 30, 2017, at 8:28 AM, Matt Sicker wrote: > > https://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.logging.log4j%22%20AND%20a%3A%22log4j-api%22 > https://search.mave

Re: [jira] [Resolved] (INFRA-14645) node requirements for jenkins job logging-log4net

For what it is worth, if you go to https://repository.apache.org/#central-stat you can see that about 25% of the downloads for log4j-api are for versions that still support Java 6. Unfortunately, I don’t know of any way to detect how many users are s

Re: [VOTE] Release Log4j 2.9.0-rc1

ogging.log4j.core.config.Configurator.initialize(Configurator.java:188) > > On Sat, Aug 26, 2017 at 10:45 PM, Ralph Goers > wrote: > >> This is a vote to release Log4j 2.9.0 the next version of the Log4j 2 >> project. >> >> Please download, test, and cast your vot

Re: [VOTE][RESULT] Log4j 2.9.0-rc1

> > Remko > >> On Aug 30, 2017, at 14:43, Ralph Goers wrote: >> >> The vote to release Log4j 2.9.0 based on release candidate 1 has passed with >> +1 votes from Gary Gregory, Matt Sicker, Mikael Ståldal, Remko Popma, and >> Ralph Goers. No other

[ANNOUNCE] Apache Log4j 2.9.0 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.9.0 release! Apache Log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many other modern features such as

Re: [VOTE] Release Log4j 2.9.0-rc1

<https://git-wip-us.apache.org/repos/asf/logging-log4j2.git>>" and then "git checkout tags/log4j-2.9-rc1” b) for an existing working copy to “git pull” and then “git checkout tags/log4j-2.9-rc1” > On Aug 31, 2017, at 12:46 PM, Mikael Ståldal wrote: > > How can I do t

Re: [Log4j] Public beta release

Yup. Besides, what is the difference between creating a release named 2.9.0-beta1 and 2.9.0 at this point. The release process is exactly the same. In addition, even if you do that I guarantee you will still find minor issues right after the non-beta release. Betas make sense when you are relea

Announcement is ugly

/www-announce/201708.mbox/%3ccd8b8bef-882e-fb69-6e89-d72428416...@apache.org%3E <http://mail-archives.us.apache.org/mod_mbox/www-announce/201708.mbox/%3ccd8b8bef-882e-fb69-6e89-d72428416...@apache.org%3E>. Any ideas? Ralph > On Aug 30, 2017, at 5:26 PM, Ralph Goers wrote: > > The

Re: Announcement is ugly

Update JAnsi from 1.14 to 1.15. > - LOG4J2-1877 <https://issues.apache.org/jira/browse/LOG4J2-1877>: > Missing documentation for Max index limit in DefaultRolloverStrategy. > Thanks to Chandra Tungathurthi. > - LOG4J2-1899 <https://issues.apache.org/jira/browse/LOG4J2-18

Log4j-audit

I just pushed the initial commit of Log4j Audit. It is by no means “done” but I am using it to perform some audit logging In a production environment. Unfortunately, the next major item I need to work on is the documentation. Right now there isn’t any, so it is going to be pretty difficult for y

Log4j support for Tomcat, TomEE, JBoss, etc.

On the commons list I got some pointers on how to integrate with Tomcat 8.5+ and TomEE. I’ve written the class that is required but am wondering where to put it. It could go in log4j-core, but that isn’t where we have been putting these things. It really shouldn’t go in log4j-web as users may no

Re: [Log4j] Broken link to ScalaDoc on site

Should that page even be in the manual any more? Ralph > On Sep 6, 2017, at 12:23 PM, Mikael Ståldal wrote: > > The ScalaDoc link on > https://logging.apache.org/log4j/2.x/manual/scala-api.html is broken. > >

Re: Log4j support for Tomcat, TomEE, JBoss, etc.

odule log4j-javaee, and to put it in the main > repo. > > > On 2017-09-06 20:49, Ralph Goers wrote: >> On the commons list I got some pointers on how to integrate with Tomcat 8.5+ >> and TomEE. I’ve written the class that is required but am wondering where to >> p

Re: Log4j-audit

nd on JavaEE stuff. > > * Is the catalog.json supposed to be written/edited by hand? > > > On 2017-09-03 04:21, Ralph Goers wrote: >> I just pushed the initial commit of Log4j Audit. It is by no means “done” >> but I am using it to perform some audit logging In a production e

Re: Log4j-audit

ould only be necessary in log4j-catalog-jpa, right? > > I see that log4j-catalog-api and log4j-catalog-git depends on > javax:javaee-api and on Spring Framework. It would be better if those modules > didn't. > > > On 2017-09-06 22:00, Ralph Goers wrote: >> Thanks,

Re: Log4j support for Tomcat, TomEE, JBoss, etc.

That was more or less my thought. In the main repo or a different one? Ralph > On Sep 6, 2017, at 3:07 PM, Remko Popma wrote: > > log4j-container? > (To be more generic than javaee) > > >> On Sep 7, 2017, at 4:56, Ralph Goers wrote: >> >> Yes, the in

Re: Log4j support for Tomcat, TomEE, JBoss, etc.

7, 2017, at 7:39, Gary Gregory wrote: >> >> The word container is so vague... container of what? Files, Applications, >> NoSQL things? How about app-container? >> >> Gary >> >>> On Wed, Sep 6, 2017 at 4:07 PM, Remko Popma wrote: >>> >

Re: Log4J 2.9.1 release

I thought about that, but it really is a pretty minor addition - it is one class. That said, if others feel that 2.10.0 is better I am happy to accommodate. Ralph > On Sep 11, 2017, at 8:31 AM, Gary Gregory wrote: > > Hi All, > > It seems to me that the recent addition of the log4j-appserver

Re: Log4J 2.9.1 release

p all of those > dependencies in the one module. Especially since we have been talking > splitting up the core module... > > Thoughts? > > Gary > > On Mon, Sep 11, 2017 at 9:34 AM, Ralph Goers > wrote: > >> I thought about that, but it really is a pretty min

Automatic module names

I know we discussed module names in the past and decided not to go the route of modularizing now - in fact, we can’t until all of our dependencies are modularized. However, we can (and probably should) add the automatic module name as a manifest entry to each of our jars. My understanding is tha

Re: Build failed in Jenkins: Log4j 2.x #3051

Looks like you removed unused imports that aren’t unused? For some reason this feels like it has happened before. Ralph > On Sep 11, 2017, at 11:36 AM, Apache Jenkins Server > wrote: > > See > > > Changes: > > [

Re: Log4J 2.9.1 release

in minor version, so the app server support should be > in 2.10.0. > > We could also descope the app server support for now, and release 2.9.1 > without it. I think that would be good given that we had quite some > regressions in 2.9.0. > > > On 2017-09-11 17:34, Ralph

Re: Log4J 2.9.1 release

gt; On Mon, Sep 11, 2017 at 5:19 PM, Ralph Goers >> wrote: >> >>> I’d be OK with not publishing log4j-appserver right now but I’d prefer to >>> leave the module in but remove it from the parent pom so that it doesn’t >>> get built or deployed. Then I don’t

Re: Automatic module names

gory wrote: > >> On Mon, Sep 11, 2017 at 11:27 AM, Ralph Goers >> wrote: >> >>> I know we discussed module names in the past and decided not to go the >>> route of modularizing now - in fact, we can’t until all of our >> dependencies >>> are mo

Re: Automatic module names

o becomes bundleId: > org.apache.logging.log4j.foo > > On 11 September 2017 at 13:01, Gary Gregory wrote: > >> On Mon, Sep 11, 2017 at 11:27 AM, Ralph Goers >> wrote: >> >>> I know we discussed module names in the past and decided not to go the >>> route of modularizin

Re: Automatic module names

erent packages." > > (Shameless plug) Every java main() method deserves http://picocli.info > >> On Sep 12, 2017, at 13:29, Ralph Goers wrote: >> >> Actually, re-reading this again makes it clear to me that log4j-slf4j-impl >> and log4j-to-slf4j SHOULD use the

Log4j-core and Android?

We are getting Jira issues about getting log4j to work in Android. At first, all I thought was required was getting the API to function on top of Android’s logging system. However, it seems that there are some who want to use the RollingFileAppender or perhaps other appenders. The issue I have i

Re: Log4j-core and Android?

Great. But how would you do it? Ralph > On Sep 13, 2017, at 7:11 AM, Gary Gregory wrote: > > I would like to see support for Android, all in our one code base, for now. > > Gary > > On Sep 13, 2017 08:02, "Ralph Goers" wrote: > >> We are getting Ji

Re: Log4J 2.9.1 release

not, we can do a 2.9.2 to fix any > issues found. > > Then we add new features for 2.10.0. > > > On 2017-09-12 06:18, Ralph Goers wrote: >> OK. The module is commented out along with the update to changes.xml. >> Ralph >

Chainsaw

Chainsaw has been in limbo for far too long. There really is only 1 active committer on the project and he has been telling people to use the latest code in master in production, which is not acceptable by the Apache release policy. We either need to have a release performed by the time of the n

Re: [Log4j] Missing Git tag for 2.9.0 release

> On Sep 15, 2017, at 11:44 AM, Mikael Ståldal wrote: > > It seems like we miss a Git tag for the 2.9.0 release. Thanks. I forgot to add the tag after the release vote. I will do that. The rc1 tag is there. Ralph

Re: Chainsaw

Scott can polish up whatever needs to be done before a release, I can > help coordinate the release itself. I'm not too familiar with the project, > so I wouldn't know if it's release-ready or not beforehand, though. > > On 14 September 2017 at 19:46, Ralph Goers >

Re: [Log4j] Release in README.md

I have an issue with anything that references a release version in the README. Keeping that up to date requires that it manually be updated before the release to the release version and then be updated again after the release to the snapshot version. Everywhere else a version appears in things t

Re: [Log4j] Release in README.md

I am replacing the section in the README regarding Maven and Gradle with a link to the relevant web site page. Ralph > On Sep 17, 2017, at 8:24 PM, Ralph Goers wrote: > > I have an issue with anything that references a release version in the > README. Keeping that up to date requ

Re: Moving log4net-logviewer to apache

> On Sep 17, 2017, at 9:47 PM, Stefan Bodewig wrote: > > On 2017-09-09, Dominik Psenner wrote: > >> What does the community think should happen? Are there people out there who >> use log4net-logviewer or any of its binaries? > > I don't. > > https://github.com/wallymathieu/log4net-logviewer/i

[VOTE] Release Log4j 2.9.1-rc1

This is a vote to release Log4j 2.9.1, 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 welcom

Re: [VOTE] Release Log4j 2.9.1-rc1

My +1 Ralph > On Sep 18, 2017, at 12:07 AM, Ralph Goers wrote: > > This is a vote to release Log4j 2.9.1, the next version of the Log4j 2 > project. > > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the artifacts > [] -

Re: [log4j] "JDK 9 Ready"

> On Sep 21, 2017, at 7:35 AM, Gary Gregory wrote: > > Hi, > > Oracle has asked me if we have an official announcement that we are "JDK 9 > ready". Do we? > > We are listed here: > https://wiki.openjdk.java.net/display/quality/Quality+Outreach >

Re: [log4j] "JDK 9 Ready"

> On Sep 21, 2017, at 9:36 AM, Gary Gregory wrote: > > On Thu, Sep 21, 2017 at 9:39 AM, Ralph Goers > wrote: > >> >>> On Sep 21, 2017, at 7:35 AM, Gary Gregory >> wrote: >>> >>> Hi, >>> >>> Oracle has asked me if

Re: [log4j] "JDK 9 Ready"

Also, I plan on adding the manifest headers so Log4j classifies as somewhat modularized before the next release. Ralph > On Sep 21, 2017, at 1:08 PM, Ralph Goers wrote: > >> >> On Sep 21, 2017, at 9:36 AM, Gary Gregory wrote: >> >> On Thu, Sep 21, 2017 at

Re: [VOTE] Release Log4j 2.9.1-rc1

I changed it some, yes. Ralph > On Sep 21, 2017, at 2:55 PM, Remko Popma wrote: > > I started writing the blog post for 2.9.1. > Quick question: no changes to the announcement text this time, is that > correct? > > On Thu, Sep 21, 2017 at 1:12 PM, Ralph Goers

Release Announcement: General Availability of JDK 9

This was copied from another list. We stopped getting these emails when we merged all the dev lists and Rory doesn’t seem to have fixed the problem. Ralph Three items to share with you today JDK 9 General Availability GPL'd binaries from Oracle are available here: http://jdk.java.net/9

[ANNOUNCE] Apache Log4j 2.9.1 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.9.1 release! Apache Log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many other modern features such as

Java 9 module names

I have created https://issues.apache.org/jira/browse/LOG4J2-2056 to identify the module names we want to use. The effort to resolve this issue will be to add the “Automatic-Module-Name” header to the jar manifest for each of the maven modules

log4j-to-slf4j

In looking at the implementations of log4j-slf4j-impl and log4j-to-slf4j is strikes me that log4j-to-slf4j is binding to the SLF4J API while log4j-slf4j-impl is binding the SFL4J API to the log4j implementation using SLF4J’s binding mechanism. So it seems to me that instead of having log4j-to-s

Fwd: log4j-to-slf4j

ges. > > What problem are we trying to solve? > > Remko > >> On Sep 25, 2017, at 7:16, Ralph Goers wrote: >> >> In looking at the implementations of log4j-slf4j-impl and log4j-to-slf4j is >> strikes me that log4j-to-slf4j is binding to the SLF4J API while &

Re: log4j-to-slf4j

> (Shameless plug) Every java main() method deserves http://picocli.info > <http://picocli.info/> > > On Sep 25, 2017, at 8:57, Ralph Goers <mailto:ralph.go...@dslextreme.com>> wrote: > >> Well, SLF4J recently changed the binding mechanism with 1.8 in order to >

Re: Log4J 2.9.1 release

I am fine with adding new features. Ralph > On Sep 25, 2017, at 12:28 PM, Mikael Ståldal wrote: > > So, now we have released 2.9.1, and JDK 9 GA is out. Do we need an 2.9.2, or > can we go on and add features for 2.10.0? > > > On 2017-09-14 22:27, Ralph Goers wrote: &

Re: log4j-to-slf4j

n Log4j2 in my opinion. > > The Java 9 stackwalker performance would be interesting to document though, > so I am sure I will get around to it at some point. > > Remko > > >> On Sep 25, 2017, at 14:33, Ralph Goers wrote: >> >> Yes, that is what we would want

Re: log4j-to-slf4j

On Sep 25, 2017, at 6:58 PM, Matt Sicker wrote: > > Would it be possible to make a log4j-api provider that binds directly to > logback instead? > > On 25 September 2017 at 18:54, Ralph Goers > wrote: > >> I have been looking at the log4j-to-slf4j binding and am ret

Re: Binary compatibility for managers in log4j-core

Since they are not something end users would normally not be accessing via an API, I think my answer would be No, it is not essential that binary compatibility be maintained with managers. Ralph > On Oct 5, 2017, at 9:53 AM, Mikael Ståldal wrote: > > We try to keep binary compatibility for ap

Re: [Log4j] Next release?

I have a number of issues I have grabbed. I need to look through them and see what I can do. However, I want to get the Automatic-Module-Name headers in. I’ve done the work but am waiting to finalize what the names should be based on Stephen Colbourne’s recommendations. Ralph > On Oct 12, 201

Logging list for emails generated by tools

What do others think about the idea of creating a separate mailing list for emails generated by tools? This list gets a bit noisy from all the extra emails and I have a hard time filtering this list because of how some of the emails are generated. I would also say that we expect every committe

Re: [Log4j] Next release?

s weekend as I'd also > like to investigate how hard it is to cut an RC for Chainsaw as well. > > On 12 October 2017 at 15:02, Ralph Goers wrote: > >> I have a number of issues I have grabbed. I need to look through them and >> see what I can do. >> >> How

Re: Logging list for emails generated by tools

though with floods of emails coming in every > so often that I just have to skip over (e.g., rebasing a long lived branch). > > On 12 October 2017 at 15:45, Gary Gregory wrote: > >> I do not care either way. >> >> Gary >> >> On Thu, Oct 12, 2017 at 2:

Re: Build failed in Jenkins: Log4j 2.x #3117

One of the Jenkins servers must be misconfigured. Ralph > On Oct 12, 2017, at 3:37 PM, Apache Jenkins Server > wrote: > > See > > > Changes: > > [ggregory] [LOG4J2-1216] Nested pattern layout options broken. App

Re: Planning out what we can do to get Chainsaw back in the game

I’ve worked with JavaFX. It is pretty easy. I have zero interest in working with Swing. I’d prefer to get away from WebStart. I think that may have been what hung up Scott in the first place as he needed a cert. Some of the other technologies for binary deployment make sense to me. To be hones

Re: Planning out what we can do to get Chainsaw back in the game

+1 Small increments seem prudent until there is some understanding of where we want to go. Ralph > On Oct 14, 2017, at 11:10 AM, Gary Gregory wrote: > > Hi Matt, > > It seems to me that to get out of the mess we are currently in, we need to > publish something official ASAP, even it is just

Java Modules

I have committed the code for LOG4J2-2056. Log4j-api is a “real” module and has a module-info.java while all the rest that can be modularized are automatic modules. Please review and test. In order to create the module-info.java I had to do a few strange things: Module-info.java is in the log4j

Re: Java Modules

14, 2017, at 10:40 PM, Ralph Goers wrote: > > I have committed the code for LOG4J2-2056. Log4j-api is a “real” module and > has a module-info.java while all the rest that can be modularized are > automatic modules. Please review and test. > > In order to create the module-in

Re: Java Modules

multiple implementations for a service > on the module path. The emphasis is more on detecting dependencies and > encapsulation, rather than preventing misconfiguration. > > I wonder if there are other projects that use identical module names to > prevent misconfiguration. Is this a

Re: Java Modules

. Ralph > On Oct 15, 2017, at 10:35 AM, Ralph Goers wrote: > > Yes, you can target specific packages for exposure to specific modules. Yes, > we would want to move the classes that are “private” to a sub package of util > if we were to do that. > > As for the name, yes you c

  1   2   3   4   5   6   7   8   9   10   >