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

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

Java 8 also has a replacement for SimpleDateFormat that should perform much better than SimpleDateFormat. Ralph > On Oct 15, 2017, at 12:10 PM, Matt Sicker wrote: > > On 14 October 2017 at 23:34, Scott Deboy wrote: > >> Parsing time strings to their numeric values using SimpleDateFormat is >

Re: Java Modules

You are welcome to create a Jira issue and do it! Ralph > On Oct 15, 2017, at 12:50 PM, Mikael Ståldal wrote: > > On 2017-10-15 07:40, 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

Re: Logging list for emails generated by tools

I have opened a Jira issue with Infra to do this. Ralph > On Oct 13, 2017, at 12:46 PM, Mikael Ståldal wrote: > > Sounds like a good idea. > > > On 2017-10-12 22:34, Ralph Goers wrote: >> What do others think about the idea of creating a separate mailing list for

Re: Logging list for emails generated by tools

It seems there is a self-service tool to create the mailing list. Ralph > On Oct 15, 2017, at 3:15 PM, Ralph Goers wrote: > > I have opened a Jira issue with Infra to do this. > > Ralph > >> On Oct 13, 2017, at 12:46 PM, Mikael Ståldal wrote: >> >> So

Re: Logging list for emails generated by tools

The mailing list notificati...@logging.apache.org <mailto:notificati...@logging.apache.org> has been created. All committers should subscribe. Ralph > On Oct 15, 2017, at 3:22 PM, Ralph Goers wrote: > > It seems there is a self-service tool to create the mailing list. > &g

Re: Logging list for emails generated by tools

ications-subscr...@logging.apache.org to subscribe... > > Gary > > On Mon, Oct 16, 2017 at 7:53 AM, Ralph Goers > wrote: > >> The mailing list notificati...@logging.apache.org > notificati...@logging.apache.org> has been created. All committers should >> subscribe. >

Re: [Log4j] Next release?

I wouldn’t call myself an “expert”… but I will look at this. Ralph > On Oct 16, 2017, at 12:00 PM, Mikael Ståldal wrote: > > On 2017-10-12 21:36, Mikael Ståldal wrote: >> - https://issues.apache.org/jira/browse/LOG4J2-2062 (waiting for contributor >> to update his PR, will do it myself soon if

Re: Java Modules

F07-CB49-4E96-8BC7-BCC2C7F725C9__NONSTANDARDOPTIONSFORJAVAC-7D3DAA9D>) With that in mind I think we the second option and not care what the module name is that the implementation uses. Ralph > On Oct 15, 2017, at 10:39 AM, Ralph Goers wrote: > > I just remembered that option 2 wouldn’

Re: logging-log4j2 git commit: Update Mockito from 2.10.0 to 2.11.0. Build passes with 'mvn clean install'.

We dropped support for Java 6 in May of 2015. If you look at https://plumbr.eu/blog/java/java-version-and-vendor-data-analyzed-2017-edition you will see that Java 6 had about a 20% market share at that time. That sa

Re: logging-log4j2 git commit: Update Mockito from 2.10.0 to 2.11.0. Build passes with 'mvn clean install'.

dependencies compatible there, and a Java 8 > test that runs with updated dependencies that require Java 8. This would be > primarily useful in Jenkins as I wouldn't want to double the build time for > release management or development. > > On 17 October 2017 at 15:26, Ralph Goers

Re: logging-log4j2 git commit: Update Mockito from 2.10.0 to 2.11.0. Build passes with 'mvn clean install'.

Sorry - of course, you would need to use profiles to make the dependencies be specific to a particular Java version. Ralph > On Oct 17, 2017, at 5:22 PM, Ralph Goers wrote: > > Just clone the Jenkins job and configure it with Java 8. We know it builds > fine with either Java

Re: Revisiting the binary logging format idea

When you say “another component in the project” do you mean logging services project or log4j? I’d prefer to see you do this in a separate repo or at least a branch until we understand what it looks like. If it is going to apply to many things it probably makes sense to be a separate repo. Ralp

Re: Revisiting the binary logging format idea

s. Would this add a new layout in Core? Maybe we should just >> start >>> with that... then grow... >>> >>> Gary >>> >>> On Thu, Oct 19, 2017 at 9:57 AM, Matt Sicker wrote: >>> >>>> I mean in the logging services project. So it'd b

Re: Test failures in log4j-taglib

I’m not sure why that would be. AFAIK that hasn’t been modified in a long time. Ralph > On Oct 19, 2017, at 12:15 PM, Mikael Ståldal wrote: > > I get a bunch of these errors in log4j-taglib when trying to build current > master branch locally: > > [ERROR] Errors: > [ERROR] CatchingTagTest.s

Re: Test failures in log4j-taglib

s dependency: > > >javax.servlet >servlet-api >2.5 >provided > > > That's causing the issue, when I changed it to 3.0.1 the test pass. Is there > any particular reason for keeping this at version 2.5? > > > On 2017-10-19 21:27, Ralph Go

Re: Test failures in log4j-taglib

So does this mean that log4j-taglib no longer supports servlet 2.5? How did this happen with no changes? Ralph > On Oct 23, 2017, at 8:21 AM, Gary Gregory wrote: > > On Thu, Oct 19, 2017 at 2:14 PM, Ralph Goers <mailto:ralph.go...@dslextreme.com>> > wrote: > >&

Re: Test failures in log4j-taglib

> On 2017-10-23 20:14, Ralph Goers wrote: >> So does this mean that log4j-taglib no longer supports servlet 2.5? How did >> this happen with no changes? >> Ralph >>> On Oct 23, 2017, at 8:21 AM, Gary Gregory wrote: >>> >>> On Thu, Oct 19, 201

Re: [Log4j] Next release?

> > On 2017-10-12 22: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. >> However, I want to get the Automatic-Module-Name headers in. I’ve done the >> work but am waiting to finalize what the

Re: Release 2.10.0?

I should be able to do it in the next few days. Ralph > On Nov 6, 2017, at 8:01 AM, Gary Gregory wrote: > > Hi All: > > We've got quite a list in changes.xml already for the next release. > > Does anyone have time to RM? > > Gary

Re: [meta] Draft blog post about logging in general

Did you change the article link? Ralph > On Nov 6, 2017, at 9:00 AM, Matt Sicker wrote: > > Post has been published: http://musigma.org/logging/2017/11/06/logging.html > > On 3 November 2017 at 22:55, Ole Ersoy wrote: > >> Wow - That looks REALLY USEFUL. BTW - Mangnus Larsson has this real

Re: [PROPOSAL] New module log4j-jetty

That is exactly what log4j-appserver is for. Right now it contains the hook for Tomcat 8.5. Having that class in a jar that also contains the hook for Jetty shouldn’t cause any problems. Ralph > On Nov 9, 2017, at 8:55 AM, Gary Gregory wrote: > > I would like to propose we add a new module ca

Re: [PROPOSAL] New module log4j-jetty

st because I > am depending on log4j-appserver's one class for Jetty logging. > > Gary > > On Thu, Nov 9, 2017 at 9:22 AM, Ralph Goers > wrote: > >> That is exactly what log4j-appserver is for. Right now it contains the >> hook for Tomcat 8.5. Having that class

Re: [PROPOSAL] New module log4j-jetty

Oops. It should be marked as provided. Almost the same effect though. Ralph > On Nov 9, 2017, at 10:44 AM, Ralph Goers wrote: > > The dependency on Tomcat should have been marked optional. That is my mistake. > > Ralph > >> On Nov 9, 2017, at 10:34 AM, Gary Gregory

Re: [PROPOSAL] New module log4j-jetty

server to log4j-tomcat and add log4j-jetty? > > Gary > > On Thu, Nov 9, 2017 at 10:45 AM, Ralph Goers > wrote: > >> Oops. It should be marked as provided. Almost the same effect though. >> >> Ralph >> >>> On Nov 9, 2017, at 10:44 AM, Ralph Go

Re: [PROPOSAL] New module log4j-jetty

in is an orthogonal concern. We > already have plenty of repos IMO, I don't want to track another one, but > hey, that's just me. If log4j-appserver is OK in the main repo, so should > log4j-jetty. > > Gary > > On Thu, Nov 9, 2017 at 1:07 PM, Ralph Goers > wrote: >

Re: [PROPOSAL] New module log4j-jetty

> On Nov 9, 2017, at 2:34 PM, Gary Gregory wrote: > > On Thu, Nov 9, 2017 at 1:49 PM, Ralph Goers > wrote: > >> Every module equates to another jar. I just don’t see why we need a jar >> for one class where a jar with 2 (as well as classes for other app servers) &g

Re: logging-log4j2 git commit: LOG4J2-2106 Reduce locking when checking for rollover

p-us.apache.org/repos/asf/logging-log4j2/diff/aad2f132 > > Branch: refs/heads/master > Commit: aad2f132b27f9e2667c2b43fb58ce59e3914edb3 > Parents: 0dca987 > Author: Ralph Goers > Authored: Fri Nov 10 06:46:11 2017 -0700 > C

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

The web site doesn’t have to be locked into the release. An image can be updated after the release pretty easily. Ralph > On Nov 10, 2017, at 1:03 PM, Scott Deboy wrote: > > Would it be possible for me to push an updated screenshot and re-spin? > > On 11/10/17, Scott Deboy wrote: >> Wow th

Re: logging-log4j2 git commit: LOG4J2-2106 Reduce locking when checking for rollover

Ok. I’m waiting on feedback on this before I start a release. Ralph > On Nov 11, 2017, at 7:14 AM, Remko Popma wrote: > > I’ll take a look tomorrow. > > > >> On Nov 10, 2017, at 22:47, Ralph Goers wrote: >> >> Please review this commit as I want to

Re: logging-log4j2 git commit: LOG4J2-2106 Reduce locking when checking for rollover

n central at > apache or do I need to build and install locally to test? > > thanks > > On 11/11/2017, 18:32, "Ralph Goers" wrote: > >Ok. I’m waiting on feedback on this before I start a release. > >Ralph > > > > Senior Softwar

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

Sure. Look at TomcatLogger. It does exactly what you are trying to do. Ralph > On Nov 11, 2017, at 2:02 PM, Gary Gregory wrote: > > The Javadoc for Log4j's LoggerAdapter says "This registry should not be > used for Log4j Loggers; it is instead used for creating bridges to other > external log s

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

Oh, but you probably don’t want to extend AbstractLogger. You really want the FQCN of the caller to be able to identify the ClassLoader and LoggerContext to use and you won’t get that from AbstractLogger’s getLogger method. Ralph > On Nov 11, 2017, at 2:45 PM, Ralph Goers wrote: >

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

ght. > > Gary > > On Sat, Nov 11, 2017 at 2:54 PM, Ralph Goers > wrote: > >> Oh, but you probably don’t want to extend AbstractLogger. You really want >> the FQCN of the caller to be able to identify the ClassLoader and >> LoggerContext to use and you won’t

Re: Jenkins build is still unstable: Log4j 2.x #3170

I am not sure why this is suddenly failing with a permission denied trying to create /tmp/hadoop.log. But why is it trying to create a file there instead of under the target directory? Ralph > On Nov 12, 2017, at 2:39 PM, Apache Jenkins Server > wrote: > > See >

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

It feels to me that this whole topic has gotten side-tracked. I think you first need to decide what you want to build before you decide on technologies. Are you building a web application or a desktop? Of course, there might be technology that lets you do both, to some degree. As far as I k

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

Are you planning on fixing this? Ralph > On Nov 11, 2017, at 5:15 PM, Ralph Goers wrote: > > Because the caller of newLogger(name) is AbstractLogger its ClassLoader will > always be used. You need the ClassLoader of the caller of getLogger(). > > Ralph > >> On Nov

Re: [log4j2] org.apache.logging.log4j.appserver.tomcat.TomcatLogger.serialVersionUID

I copied the file from somewhere else in Log4j and it had it. Ralph > On Nov 13, 2017, at 11:00 AM, Gary Gregory wrote: > > Why does the Tomcat logger > define org.apache.logging.log4j.appserver.tomcat.TomcatLogger.serialVersionUID > ? > > Is that class serializable even though it is not decla

Log4j 2.10

Unless someone objects I plan to start the release process for Log4j 2.10 tomorrow. I had wanted to include a fix for LOG4J2-2106 but the problem only occurs in rare situations and I am not sure how to fix it yet. There are a lot of other issues that deserve looking at but nothing I can see that

Re: logging-log4j2 git commit: Update Maven site plugin from 3.4 to 3.6.

Out of curiosity did you build the site after you update the dependency to verify there aren’t any problems? Ralph > On Nov 13, 2017, at 6:12 PM, ggreg...@apache.org wrote: > > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 661c80671 -> 9218cba93 > > > Update Maven site p

Re: logging-log4j2 git commit: Update Maven site plugin from 3.4 to 3.6.

Oops. Nevermind. I see you downgraded it again. Ralph > On Nov 15, 2017, at 9:33 PM, Ralph Goers wrote: > > Out of curiosity did you build the site after you update the dependency to > verify there aren’t any problems? > > Ralph > >> On Nov 13, 2017, at 6:12 PM

Re: Compression on rolling leads to OOM

“async logging”). There are some >>>>> situations where due to spikes in the volume of requests, the >>> compression >>>>> on rolling creates memory starvation. >>>>> >>>>> Now, a straight forward fix would to remove it from th

Re: Compression on rolling leads to OOM

Sure, why not? Ralph > On Nov 16, 2017, at 11:24 AM, Chandra > wrote: > > with-in log4j? > > On 16 Nov 2017, 11:46 PM +0530, Ralph Goers , > wrote: >> I could see forking a process instead of spawning a thread to perform the >> compression as a viable appr

Re: Compression on rolling leads to OOM

I should have used “spawn” instead of “fork”. Ralph > On Nov 16, 2017, at 11:34 AM, Matt Sicker wrote: > > I don't think Java supports process forking (not even sure if Windows > does), but you can execute and control processes at least. > > On 16 November 2017 at 12:2

Re: Compression on rolling leads to OOM

en sure if Windows >> does), but you can execute and control processes at least. >> >> On 16 November 2017 at 12:28, Ralph Goers > wrote: >> >>> Sure, why not? >>> >>> Ralph >>> >>>> On Nov 16, 2017, at 11:24 AM, Ch

Re: Log4j 2.10

Well, I thought I would have time today but it is rapidly getting away from me. I will have time on Saturday for sure. Ralph > On Nov 16, 2017, at 1:38 PM, Mikael Ståldal wrote: > > OK for me. Thanks for the RM work. > > > On 2017-11-16 05:31, Ralph Goers wrote: >>

Re: Jenkins build is still unstable: Log4j 2.x #3170

get this working again. (I am not sure how to access the Jenkins > machine to be able to do that.) > > > On 2017-11-12 23:58, Ralph Goers wrote: >> I am not sure why this is suddenly failing with a permission denied trying >> to create /tmp/hadoop.log. But why is it tr

Failing unit test

I am preparing to do the release build and am getting the following error: Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.25 s <<< FAILURE! - in org.apache.logging.log4j.core.appender.SyslogAppenderTest testTCPAppender(org.apache.logging.log4j.core.appender.SyslogAppenderTest)

Re: Failing unit test

finishing all the tasks. Ralph > On Nov 19, 2017, at 9:07 AM, Mikael Ståldal wrote: > > I made an attempt to make that test more reliable. > > On 2017-11-19 00:57, Ralph Goers wrote: >> I am preparing to do the release build and am getting the following error: >>

[VOTE] Release Log4j 2.10.0-rc1

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

Re: [VOTE] Release Log4j 2.10.0-rc1

; [ERROR] > testCallReturnsNullAndPrintsErrorIfParseFails(org.apache.logging.log4j.core.tools.picocli.CommandLineTest) > Time elapsed: 0.04 s <<< FAILURE! > org.junit.ComparisonFailure: > expected:<...t a number" > Usage: [ [-number=] > -number=] >> b

Re: [VOTE] Release Log4j 2.10.0-rc1

gt; [INFO] Final Memory: 56M/518M > [INFO] > > > > > On Mon, Nov 20, 2017 at 2:10 PM, Remko Popma wrote: > >> When I upgraded picocli to 2.0.3 a few weeks ago I made sure all tests >> passed

Re: [VOTE] Release Log4j 2.10.0-rc1

17-11-20T14:56:18+09:00 > [INFO] Final Memory: 56M/518M > [INFO] > > > > > On Mon, Nov 20, 2017 at 2:10 PM, Remko Popma wrote: > >> When I upgraded picocli to 2.0.3 a few weeks ago I made su

Re: [VOTE] Release Log4j 2.10.0-rc1

Oops - Greg s/b Gary. Ralph > On Nov 19, 2017, at 11:21 PM, Ralph Goers wrote: > > Oh, and I wouldn’t be surprised if the problem is caused by you using MS932 > and Greg using cp1252. > > Ralph > > >> On Nov 19, 2017, at 11:12 PM, Remko Popma wrote: >>

Re: [VOTE] Release Log4j 2.10.0-rc1

>>> [INFO] Apache Log4J Performance Tests ..... SUCCESS [ >>> 58.354 s] >>> [INFO] Apache Log4j Streaming Interface ... SUCCESS [ >>> 15.511 s] >>> [INFO] Apache Log4j JUL Adapter ... SUCCESS [ >&g

Re: [VOTE] Release Log4j 2.10.0-rc1

73 s] >>> [INFO] Apache Log4j Cassandra . SUCCESS [ >>> 27.022 s] >>> [INFO] Apache Log4J Performance Tests . SUCCESS [ >>> 58.354 s] >>> [INFO] Apache Log4j Streaming Interface ... SUCCESS [ >>> 15.511 s] >>&g

Re: [VOTE] Release Log4j 2.10.0-rc1

t;>>> 9.422 s] >>>> [INFO] Apache Log4j BOM ... SUCCESS [ >>>> 1.082 s] >>>> [INFO] Apache Log4j CouchDB ... SUCCESS [ >>>> 2.306 s] >>>> [INFO] Apache Log4j MongoDB ... S

Re: [VOTE] Release Log4j 2.10.0-rc1

that's the way it (currently) is. > > >> On 2017-11-20 20:33, Gary Gregory wrote: >> It's just lame that if someone downloads the source they cannot even build >> it :-( >> Gayr >>> On Mon, Nov 20, 2017 at 2:28 PM, Mikael Ståldal wrote: >>> I agr

Re: [VOTE] Release Log4j 2.10.0-rc1

compile the source code for Java libraries, >> I usually just skip tests. >> >> On 20 November 2017 at 13:50, Ralph Goers >> wrote: >> >>> More like 4 hors >>> >>> Sent from my iPhone >>> >>>> On Nov 20, 2017, at 12:

Re: [VOTE] Release Log4j 2.10.0-rc1

Here is my +1 Ralph > On Nov 20, 2017, at 10:38 PM, Ralph Goers wrote: > > I have fixed the page on my GitHub site. > > Ralph > >> On Nov 20, 2017, at 7:36 PM, Remko Popma wrote: >> >> +1 >> checksums good, build good, site good other than H3 on

[VOTE][RESULT] Release Log4j 2.10.0-rc1

This vote has passed with binding +1 votes from Mikael Ståldal, Matt Sicker, Remko Popma, and Ralph Goers, a binding -1 from Gary Gregory, and a non-binding +1 from Daan Hoogland. I will continue with the release process. Ralph

Re: converting markdown links to html links

Thanks, although the announcement is going to contain a bit more text than is in the release notes. Ralph > On Nov 23, 2017, at 12:06 AM, Remko Popma wrote: > > This took me a while to get right, so let me share it. > > Below unix command can be used to replace the markdown links to HTML link

Re: converting markdown links to html links

Those are. I am going to hand-edit the announcement. Ralph > On Nov 23, 2017, at 1:06 AM, Remko Popma wrote: > > Really? > Looking at announcement.vm they seem identical. > > > >> On Nov 23, 2017, at 16:59, Ralph Goers wrote: >> >> Thanks, although

Re: Log4JNA

Or ask the author if he would like it to become part of Logging Services. Ralph > On Nov 23, 2017, at 7:51 AM, Gary Gregory wrote: > > On Thu, Nov 23, 2017 at 4:10 AM, Remko Popma wrote: > >> Interesting: >> https://github.com/dblock/log4jna/blob/master/README.md >> >> Maybe we should link t

[ANNOUNCEMENT] Apache Log4j 2.10.0 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.10.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: Log4JNA

Why can’t we move some of the stuff in core to another project? Ralph > On Nov 23, 2017, at 12:00 PM, Gary Gregory wrote: > > I really like the use of JNA! This could be another module. > > Gary > > On Nov 23, 2017 13:20, "Ralph Goers" wrote: > >>

Re: [Log4j] Wrong version of Scala API in documentation

You can also directly fix the web site. See https://wiki.apache.org/logging/ManagingTheWebSite . You only need to check out the log4j directory and the specific version you want to modify. Ralph > On Nov 25, 2017, at 7:52 AM, Mikael Ståldal

Re: [Log4j] ProcessIdUtil

It is there because there is a Java 9 version of it and I did not want to make multiple Java 9 modules. Ralph > On Nov 25, 2017, at 7:54 AM, Mikael Ståldal wrote: > > Regarding https://issues.apache.org/jira/browse/LOG4J2-2126 > > Why is ProcessIdUtil in log4j-api in the first place? It is on

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

It is not a problem with our build. I am not sure why it is occurring. Ralph > On Nov 25, 2017, at 8:34 AM, Mikael Ståldal wrote: > > What does this mean? Is this a problem in our build, or a temporary > infrastructure problem? > > > On 2017-11-25 16:01, Apache Jenkins Server wrote: >> ERROR

Re: Git tag for 2.10.0

Yup. I forgot to do it. I will do it when I get home from work. Ralph > On Nov 27, 2017, at 8:20 AM, Gary Gregory wrote: > > I do not see a Git tag for 2.10.0 yet. > > Gary

Re: [Log4j] Closing resolved JIRA issues

They should be automatically closed after a “reasonable” period of time. I’m not sure wha the definition of reasonable is. Ralph > On Nov 30, 2017, at 12:46 PM, Mikael Ståldal wrote: > > How should we handle closing of resolved JIRA issues? > > Idealy, the original reporter should close after

Re: [Log4j] Apache HttpClient 5, Log4j and Slf4j

I see several issues: StackLocator: This cannot be removed from the API is the API as LogManager.getLogger() calls it. Converting the Java 9 version to use Reflection would add enough overhead that it probably wouldn’t be worth it to use it. Also, you would have to figure out how to cod

Re: [Log4j] Apache HttpClient 5, Log4j and Slf4j

FWIW, it would make sense to me to make a log4j-core-android that is a subset of what is in core, if that is possible. Of course, the API problem has to be solved first. Ralph > On Dec 2, 2017, at 9:38 AM, Ralph Goers wrote: > > I see several issues: > > StackLocator: >

SLF4J now requires Java 6

And here you are complaining we haven’t moved to Java 8 as the minimum... http://slf4j.42922.n3.nabble.com/qos-ch-slf4j-5f0078-slf4j-api-now-requires-Java-6-td4026870.html Ralph

Re: [Log4j] Apache HttpClient 5, Log4j and Slf4j

sworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:415) >at org.codehaus.plexus.classworlds.launcher.Launcher.main > (Launcher.java:356) > > Gary > > On Sat, Dec 2, 2017 at 11:49 AM, Gary Gregory > wrote: > >> I think Slf4j 1.8-alpha has the same probl

Re: [Log4j] Apache HttpClient 5, Log4j and Slf4j

I suppose we could have the log4j-api have a transitive dependency on log4j-api-java9 only when the build target is Java 9. Ralph > On Dec 2, 2017, at 3:03 PM, Ralph Goers wrote: > > So this is the other problem. It is complaining that it doesn’t support Java > 9 class files. T

Re: [Log4j] Apache HttpClient 5, Log4j and Slf4j

Let’s go back to this post. Assume we figured out how to get rid of all the stuff you consider to be not required to be in the API. Even if we did that it still would not work in Android so long as the API contains module-info.java, because that class can only be compiled for Java 9. So ther

Re: SLF4J now requires Java 6

In theory… Ralph > On Dec 3, 2017, at 11:11 AM, Matt Sicker wrote: > > Plus the whole multi-version jars feature is super handy for a library like > Log4j which can add support for each new Java version while maintaining BC > with older Java releases without having to resort to reflection hacks

Build failure

I am getting this test failure when building core. [ERROR] Failures: [ERROR] CommandLineTest.testInetAddressConvertersInvalidError:476->parseInvalidValue:492 Invalid format %$::a?*!a was accepted for -InetAddress Ralph

Re: [log4j] providing sourcewith Message

I don’t understand how this is a good idea. To use this you would need to do something like: Message msg = new StringMessage(getCaller(), “My Message”); logger.debug(msg); Unfortunately the line number would point to the line where getCaller() is called not to the logger statement. I had thoug

Re: [Log4j] Next release?

It will be 2.10.1 unless we have new features to add that warrant a minor version bump. Do you have new features to add? Ralph > On Dec 11, 2017, at 11:54 AM, Mikael Ståldal wrote: > > Do we plan to do a 2.10.1, or will next release be 2.11.0? >

Re: Errors in OSGi tests

I haven’t seen those but no one ever replied on the error I posted last week. Ralph > On Dec 12, 2017, at 12:56 PM, Gary Gregory wrote: > > Does anyone else see this with git master: > > [ERROR] Errors: > [ERROR] > EquinoxLoadApiBundleTest>AbstractLoadBundleTest.testMissingImportOfCoreOsgiPack

Re: [Log4j] Incorrect information about markers in SLF4J documentation

Yes, that is indeed incorrect and should be reported. Ralph > On Dec 19, 2017, at 1:35 PM, Mikael Ståldal wrote: > > I just realized that the documentation for SLF4J contain incorrect > information about markers: > > https://www.slf4j.org/faq.html#marker_interface > https://www.slf4j.org/faq.

Re: [log4j] providing sourcewith Message

gt;>>>>>> >>>>>>>> after: >>>>>>>> def f() = logger.traced(Level.INFO) {...} >>>>>>>> >>>>>>>>> On Mon, Dec 11, 2017 at 9:55 PM, Matt Sicker >> >>>>> wrote: >

[log4j] getCallerClass()

Reflection.getCallerClass() has been removed in Java 10 [1]. The pre-Java 9 version is already sensitive to this so it shouldn’t cause any problems. Ralph [1] http://mail.openjdk.java.net/pipermail/core-libs-dev/2017-December/050713.html

Re: [log4j] providing sourcewith Message

ent requires a method name. I'll double > check this. > > On Thu, Dec 21, 2017 at 12:40 AM, Ralph Goers > wrote: > >> I’m not sure I would be comfortable applying the patch this way. Have you >> run a clirr report on your changes? I am concerned that this could break

Re: [log4j] release 2.10.1

I reported that the build failed for me 2 weeks ago and never heard anything. I just tried it again and now I get a failure in log4j-api. I can’t perform releases while there are build failures. [ERROR] Tests run: 53, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.929 s <<< FAILURE! - in o

Re: [log4j] release 2.10.1

PPED > [INFO] Apache Log4j JUL Adapter ... SKIPPED > [INFO] Apache Log4j Liquibase Binding ..... SKIPPED > [INFO] Apache Log4j App Server Support SKIPPED > [INFO] > ---

Re: [log4j] release 2.10.1

I am using the same version of Maven and Java. Does your reactor order match mine? [INFO] Reactor Summary: [INFO] [INFO] Apache Log4j 2 . SUCCESS [ 1.532 s] [INFO] Apache Log4j API Java 9 support SUCCESS [ 4.568 s] [INFO] Apache Log4j AP

Java 9 compile failure

I just want to thank Gary for getting https://issues.apache.org/jira/browse/MCOMPILER-308 created. That got Robert to create https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8191322

Re: [Log4j] release 2.10.1

I’ve turned my attention to Log4j Audit and hope to finish that up before returning to work next week. I will be taking vacation for a week starting next weekend and don’t plan on doing any releases at that time. Ralph > On Dec 30, 2017, at 12:29 PM, Gary Gregory wrote: > > Hi All, > > And

Re: [log4j] and Apache HttpClient

I have a couple of comments here. One of the reasons I created Log4j using its own API was due to the introduction of Messages. I had discussions on the SLF4J list that made it clear that Ceki wasn’t interested in modifying the API to support anything more than Strings. In fact, as a whole SLF4

Re: [log4j] and Apache HttpClient

I am on PTO this week. I might find time for this when I am not out having fun Sent from my iPhone > On Jan 8, 2018, at 11:24 AM, Mikael Ståldal wrote: > > I think that we should at least make a release with fix for > https://issues.apache.org/jira/browse/LOG4J2-2126 before we try to convince

Re: Event batch

The actual code in the AsyncAppender does: public void append(final LogEvent logEvent) { if (!isStarted()) { throw new IllegalStateException("AsyncAppender " + getName() + " is not active"); } final Log4jLogEvent memento = Log4jLogEvent.createMemento(logEvent, includeLocation

Re: Event batch

Also, note that each event has to be individually filtered so processing a batch probably won’t work properly. Ralph > On Jan 9, 2018, at 8:04 AM, Ralph Goers wrote: > > The actual code in the AsyncAppender does: > > public void append(final LogEvent logEvent) { >

  1   2   3   4   5   6   7   8   9   10   >