Re: [VOTE] Release Log4Net 2.0.9

t;>>>> them. >>> >>>>>>>> >>> >>>>>>>> On Sat, Aug 22, 2020, 20:39 Davyd McColl wrote: >>> >>>>>>>> >>> >>>>>>>>> I know I'm quite ne

Log4Net Web site

All the NuGet emails are forwarded to the Logging PMC. We are getting requests to see the changes between 2.0.8 and 2.0.9. In the future I would suggest we not push to NuGet until the web site is updated. To avoid this. Ralph

Re: Log4Net Web site

Davyd, Can you update the web site? It still says Log4Net is dormant and does not include any info about 2.0.0. The PMC is continuing to get queries since there is no public info about the release. Ralph > On Aug 24, 2020, at 3:31 PM, Ralph Goers wrote: > > All the NuGet e

Re: Time-sensitive tests

You probably need to look at the logic of the tests. Some of these expect a certain number of files or records in each file and that may not always be the case in the first or last interval. Ralph > On Aug 26, 2020, at 12:47 AM, Volkan Yazıcı wrote: > > I have been trying to fix certain (rand

Re: Log4Net Web site

wrote: >> >> Ralph, I'm happy to -- but I have no idea how to. Even a pointer at a >> document I can read on how would be greatly appreciated (ie how to get >> content to the website) >> >> -d >> >> On 2020/08/26 16:54:46, Ralph Goers wrot

Re: Log4Net Web site

you how to update the public site. But first you have to get the site build working again. Ralph > On Aug 26, 2020, at 8:17 AM, Ralph Goers wrote: > > Actually, I can handle the main web site. I just need the Log4Net site > updated. From what I can tell it uses the Maven site

Re: Log4Net Web site

27;t seem to e referenced (that I could find via a quick > text-search). > > I'll report back when I have something that works. > > -d > > On 2020/08/26 17:26:18, Davyd McColl wrote: > Thanks Ralph, will give that all a go tonight! > -d > > On August 26, 20

Re: Log4Net Web site

7;m also not sure how a changelog ends up in the site, since the > changes folder doesn't seem to e referenced (that I could find via a quick > text-search). > > I'll report back when I have something that works. > > -d > > On 2020/08/26 17:26:18, Davyd McCo

Re: JsonTemplateLayout is ready to be shipped!

I should add that I also promised to help get the Log4Net site deployed and to move the web site off of the CMS, so I may do those before creating a release. Ralph > On Aug 27, 2020, at 6:54 AM, Apache wrote: > > No, you are not expected to do anything else. While anyone can be the release >

Re: A little stuck with publishing updated site / docs for log4net 2.0.9

I have updated the logging services site and corrected log4net’s .htaccess file to point to the 2.0.9 release. However, I cannot seem to get the download page to reference 2.0.9. It still shows 2.0.8. The release notes are correct though. Ralph > On Aug 28, 2020, at 7:38 AM, Davyd McColl wrot

Re: [Log4j] Test failures in master

That depends on what the error is. In general fixing errors is better than sweeping them under the rug. I am not sure when I will get a chance to look into it myself. Ralph > On Aug 29, 2020, at 12:52 PM, Matt Sicker wrote: > > It seems like all the Equinox OSGi tests are failing with an erro

Re: Your project website

I have created the logging site in git at https://github.com/apache/logging-site . I used jbake to generate the CMS portion of the site. It is pretty easy. All you have to do is cd sources Make the required changes mvn install You will then hav

Re: Your project website

b site using svn has been taking at least 30 minutes. My experience in committing the preview site to my personal GitHub site has shown that it is significantly faster. Ralph > On Aug 30, 2020, at 11:29 AM, Ralph Goers wrote: > > I have created the logging site in git at > https:/

Re: Your project website

et me know if you see any other problems. Ralph > On Aug 30, 2020, at 10:21 PM, Ralph Goers wrote: > > Another follow-up. After a discussion on Slack with infra I determined that > using GitHub pages isn’t what we want to do. I then modified the site to work > with the normal

Re: Your project website

g else looks good. > > On Mon, 31 Aug 2020 at 13:31, Ralph Goers <mailto:ralph.go...@dslextreme.com>> wrote: >> >> The logging site is now working properly. Please look at >> http://logging.staged.apache.org <http://logging.staged.apache.or

Re: Your project website

> On Aug 31, 2020, at 1:15 PM, Ralph Goers wrote: > > The download link for Log4net is wrong even for the live site. For some > reason it doesn’t seem it was updated during the release process. > > Ralph > >> On Aug 31, 2020, at 11:47 AM, Matt Sicker wrote: &

Re: Your project website

e will be committed to git instead of > svn? > > -Robert Middleton > > On Mon, Aug 31, 2020 at 4:15 PM Ralph Goers > wrote: > >> The download link for Log4net is wrong even for the live site. For some >> reason it doesn’t seem it was updated during the release pr

Re: GitHub Pages (Was: Your project website)

regarding your "after a discussion on Slack with infra I determined >> that using GitHub pages isn’t what we want to do." remark... I am curious >> to know about the details. Can we use GitHub pages in some way? Or why one >> should prefer one over another? >> >

Re: svn commit: r1065013 - /websites/production/logging/content/log4net/log4net-2.0.9/download_log4net.html

FWIW, this change won’t have any effect as I asked infra to decommission the CMS-based web site. You need to make the modifications in the GitHub repo. Ralph > On Aug 31, 2020, at 11:16 PM, dav...@apache.org wrote: > > Author: davydm > Date: Tue Sep 1 06:16:14 2020 > New Revision: 1065013 > >

Re: Your project website

e changing or if something else is messed up. >> >> I assume this means now that the site will be committed to git instead of >> svn? >> >> -Robert Middleton >> >> On Mon, Aug 31, 2020 at 4:15 PM Ralph Goers >> wrote: >> >>> The down

Re: [VOTE] Release Log4Net 2.0.9

I also just noticed that the git repo has no tag to represent 2.0.9. Without a tag essentially there is no release. Ralph > On Aug 24, 2020, at 3:27 PM, Ralph Goers wrote: > > The release isn’t done yet. The web site still reflects 2.0.8. Release > announcements can’t be se

Re: [VOTE] Release Log4Net 2.0.9

OK, I’ve looked at http://logging.staged.apache.org/log4net. The download page still doesn’t look correct. The heading still says 2.0.8 although the source zip is 2.0.9 as it should be. The binary artifacts display as 2.0.8 but the links point to 2.0.9. Log4j controls all of this with a variabl

Re: [VOTE] Release Log4Net 2.0.9

ce; pushed to asf-staging & checked on > http://logging.staged.apache.org/log4net. > > -d > On 2020/09/05 08:12:19, Ralph Goers wrote: > OK, I’ve looked at http://logging.staged.apache.org/log4net. The download > page still doesn’t look correct. The heading still says 2.

Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

For some reason all messages from NuGet are routed to the Apache Logging PMC list. This one clearly does not need to be private. Just know that the person who sent this is apparently not subscribed to the ASF mailing lists so won’t see a response unless he is cc’d. I’m not familiar with NuGet b

Re: [NuGet Gallery] Message for owners of the package 'log4net'

reach out >>> >> > on >>> >> > email). So the possible solutions I see here are to >>> >> > - automate handling the email >>> >> > - make the issue reporting url clearer on the project page. >>> >> > >>

Re: [NuGet Gallery] Message for owners of the package 'log4net'

>>>> associated email address (which is probably why most people reach >> out on >>>>>>> email). So the possible solutions I see here are to >>>>>>> - automate handling the email >>>>>>> - make the issue reporting url cl

Re: [NuGet Gallery] Message for owners of the package 'log4net'

uld be great if there was an option to do so today. > > Can infra subscribe nuget to a mailing list without the confirmation of the > owner of the mail? > -- > Sent from my phone. Typos are a kind gift to anyone who happens to find > them. > > On Tue, Sep 8, 2020, 20:21 Ral

Re: [VOTE] [log4net] Release 2.0.10

Davyd, That makes 3 +1 PMC votes so you may proceed with the release. Please update the web site before you publish to NuGet. I will copy the artifacts to the release distribution area for you. Ralph > On Sep 11, 2020, at 8:19 AM, Dominik Psenner wrote: > > +1 > > -- > Sent from my phone.

Re: [VOTE] [log4net] Release 2.0.10

The artifacts have been committed to https://dist.apache.org/repos/dist/release/logging/log4net/. Ralph > On Sep 11, 2020, at 9:44 AM, Ralph Goers wrote: > > Davyd, > > That makes 3 +1 PMC votes so you may proceed with the release. Please update > the web site before yo

Re: [VOTE] [log4net] Release 2.0.10

staged.apache.org/log4net; however, it's ready to go whenever > it can be published. > > Thanks again > -d > > On 2020/09/12 06:00:04, Ralph Goers wrote: > The artifacts have been committed to > https://dist.apache.org/repos/dist/release/logging/log4net/.

Re: JsonTemplateLayout is ready to be shipped!

Yeah, I rely mostly on the automation but I run the build on my Mac several times before a release and if any of them fail I wouldn’t even start the release process. I still am working on my $dayjob project and would still want to take a look at open Jira issues before starting the release. I wo

Re: [VOTE] [log4net] Release 2.0.10

I checked out the asf-site branch and ran “git rebase asf-staging” and then committed that. The 2.0.10 site is live. Ralph > On Sep 12, 2020, at 10:50 AM, Ralph Goers wrote: > > Davyd, > > You have full access to all Logging repos at GitHub. You can publish the > log4net

Re: JsonTemplateLayout is ready to be shipped!

cut. Ralph > On Sep 12, 2020, at 10:59 AM, Gary Gregory wrote: > > I think focusing on fixing the build should come before considering > bringing in PRs or Jira issues. I think Matt stated we don't get a clean > build ATM? > > Gary > > On Sat, Sep 12

Disable dependabot

I very much like all the emails due to dependabot. Furthermore, if it is going to create 25 PRs then it also needs to create Jira issues and include updates to changes.xml, otherwise it just creates a lot of work. Furthermore, I have never been in favor of updating dependencies versions without

Re: Disable dependabot

ntain API compatibility over time). > > On Thu, Sep 17, 2020 at 21:03 Gary Gregory wrote: > >> On Thu, Sep 17, 2020 at 8:49 PM Ralph Goers >> >> wrote: >> >> >> >>> I very much like all the emails due to dependabot. Furthermore, if it is

Re: [log4cxx] Site / Documentation thoughts

The main web site is built using JBake. Although it is Java based and still uses Maven the command to build the site is just mvn install (although it doesn’t actually do an install). All the web pages are either Markdown or AsciiDoctor. I should also add that you don’t have to use Maven. You ca

Re: [VOTE] [log4net] Release 2.0.11

In the long run you don’t want to be regenerating your signing key for every release. The point is that you would upload the key to a central keystore and other people would sign it there. At ApacheCon we would have a key signing “party” where we recorded each others keys and then would take our

Re: [VOTE] [log4net] Release 2.0.11

t key on the cli for the immediate >>> upload. >>> >>> >>> >>> My gpg key as at https://GitHub.com/fluffynuts.gpg is the same that I >>> used >>> >>> last time. >>> >>> >>> >>> -d >>&g

Re: [logging-log4j2] branch master updated (bf16de8 -> e382adb)

You will have to ask infra. Based on what I found on google it looks like there is a post commit hook to send email that uses git rev-list and based on the result of that may generate that line. From what I can see git rev-list walks up the commit tree but I don’t really know what it is trying

Re: [VOTE] [log4net] Release 2.0.11

so may need a bit of a crash intro. >> >> If posting meeting details to the mailing list is not on, feel free to >> email me directly (: >> >> -d >> >> >> On September 20, 2020 20:58:29 Ralph Goers >> wrote: >> >>> 8am in Du

Re: Batching in appenders

Well, Log4j only feeds events to Appenders one at a time. It has no place to aggregate them. However, one Appender could wrap others to create a batch at which point this would become useful. I suppose some other component could be invented to create a batch but I am not sure where or how that

Re: Batching in appenders

ble utility functionality) if we can > extract it out. > > -ck > > On Thu, Sep 24, 2020, at 11:46, Ralph Goers wrote: >> Well, Log4j only feeds events to Appenders one at a time. It has no place to >> aggregate them. However, one Appender could wrap others to create a bat

Re: Batching in appenders

> On Sep 24, 2020, at 11:48 AM, Volkan Yazıcı wrote: > > I think endOfBatch flag is still falling short of addressing the main > issue: the appender is oblivious to the batching. Put another way, it > cannot have an assumption whether endOfBatch is employed or not. Consider > appender A honori

Re: Batching in appenders

The more I think about this the more questions I have. As far as I can recall the Appenders that support batching do so because there is a distinct performance benefit to it and the underlying transport mechanism supports it. But almost every different transport handles batching differently. Fo

Re: Updating the LoggerContext using a ConfigurationSource

Try calling Configurator.initialize(null, configurationSource); Ralph > On Sep 27, 2020, at 7:40 AM, Jochen Wiedmann > wrote: > > Hi, > > in LoggerContext, I have > >void updateLoggers(Configuration); > > I understand, that this method provides the means to change the logging > config

Re: Updating the LoggerContext using a ConfigurationSource

Jochen > > On Sun, Sep 27, 2020 at 5:08 PM Ralph Goers > wrote: >> >> Try calling >> >> Configurator.initialize(null, configurationSource); >> >> Ralph >> >>> On Sep 27, 2020, at 7:40 AM, Jochen Wiedmann >>> wrote: &g

Re: Updating the LoggerContext using a ConfigurationSource

> On Sep 27, 2020, at 11:07 AM, Jochen Wiedmann > wrote: > > On Sun, Sep 27, 2020 at 6:38 PM Ralph Goers > wrote: >> >> It would not create a new LoggerContext. But a ConfigurationSource >> represents an entire configuration. So calling initial

Re: Maintaining a set of Log4j configurations

That design should be fine but you will need to implement your own ContextSelector to locate the LoggerContext from the Map. You will also need to make sure the application id is available whenever something needs to locate the LoggerContext via the ContextSelector. As I have said previously, l

Re: Ramp down for Log4j 2.14.0 release (Was: JsonTemplateLayout is ready to be shipped!)

Yes, but there is a light at the end of the tunnel. The component I am building at work has taken more than twice as long as I expected. We have gotten a few issues recently that look really important to look into. I’d like to at least have them looked into before we cut the release. Ralph

Log4j 2 Compile error

I just tried to do a full build for the first time in a while and am getting [INFO] Compiling 77 source files to /Users/rgoers/projects/apache/logging/log4j/release-2.x/log4j-perf/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INF

Re: Log4j 2 Compile error

yish, i.e., nothing new > besides already known failures: > https://github.com/apache/logging-log4j2/actions/runs/292125976 > Which OS, JDK(s)did you use? > > On Sun, 18 Oct 2020, 21:04 Ralph Goers wrote: > >> I just tried to do a full build for the first time in a whi

Re: Log4j 2 Compile error

Shoot. I just recalled that log4j-perf is compiled with Java 9+. I will have to check what is being used for that, but nothing has changed in ages. Ralph > On Oct 18, 2020, at 12:58 PM, Ralph Goers wrote: > > MacBook Pro with Catalina 10.15.6. failed with Oracle Java 8.144 and

Re: Log4j 2 Compile error

This looks like https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8193802 <https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8193802>. Ralph > On Oct 18, 2020, at 1:03 PM, Ralph Goers wrote: > > Shoot. I just recalled that log4j-perf is compiled with Java 9+. I will h

Re: Log4j 2 Compile error

Yup. Changing the toolchain version from 9 to 11 fixed it. Ralph > On Oct 18, 2020, at 1:05 PM, Ralph Goers wrote: > > This looks like https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8193802 > <https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8193802>. > &g

Re: [VOTE] [log4net] Release 2.0.11

t this out >> >>> the door because it fixes confusing versioning on the released binaries >> (in >> >>> particular, nuget consumers) >> >>> >> >>> Thanks >> >>> -d >> >>> On 2020/09/20 22:33:

Re: [VOTE] [log4net] Release 2.0.11

;> Ralph >>> >>>> On Oct 25, 2020, at 11:24 PM, Davyd McColl wrote: >>>> >>>> Thanks Ralph >>>> >>>> Could you assist with getting artifacts up to downloads.apache.org? I'm >>>> going to push the nupkg becaus

Re: [LOG4NET] Vote for release: 2.0.12

OK +1 to these. Ralph > On Oct 26, 2020, at 8:57 AM, Davyd McColl wrote: > > Ralph, here's the 2.0.12 thread where Matt and Remko voted. > > -d > > > On October 23, 2020 17:57:31 Davyd McColl wrote: > >> Thanks Matt >> >> I think I need 3 to release... Any other takers? >> >> -d >> >>

Re: [LOG4NET] Vote for release: 2.0.12

The files were added to the distribution directory. Ralph > On Oct 26, 2020, at 9:22 AM, Ralph Goers wrote: > > OK > > +1 to these. > > Ralph > >> On Oct 26, 2020, at 8:57 AM, Davyd McColl wrote: >> >> Ralph, here's the 2.0.12 thread wher

Re: Catching Throwable's in AsyncAppender worker

You are correct. Log4j should handle everything except an OOM error. Ralph > On Oct 28, 2020, at 1:05 PM, Volkan Yazıcı wrote: > > Hello, > > While logging, we sometimes notice that the entire logging infra comes to a > halt, even though the rest of the application still works perfectly fine.

Re: Catching Throwable's in AsyncAppender worker

You might as well catch Throwable. You can’t really handle out of memory errors - the JVM won’t let you. As for StackOverflowError - yes, that should be handled. We don’t want the application to fail due to a buggy logging plugin. Ralph > On Oct 28, 2020, at 2:17 PM, Gary Gregory wrote: > > H

Log4j 2.14.0 release status

I started the process of preparing for the release today. The Maven site build is failing because somehow a version named 2.14.0—SNAPSHOT was uploaded to the Nexus Snapshot repository. While investigating I noticed that there is at least one snapshot for every past release so Nexus apparently i

Re: Log4j 2.14.0 release status

I should clarify that it is the DOAP plugin that is failing. It is invoked from the site plugin. Ralph > On Oct 31, 2020, at 9:51 PM, Ralph Goers wrote: > > I started the process of preparing for the release today. The Maven site > build is failing because somehow a version

Re: Log4j 2.14.0 release status

of >> snapshots: >>> >>> >> https://repository.apache.org/content/groups/public/org/apache/logging/log4j/log4j-core/ >>> >>> Gary >>> >>>> On Sun, Nov 1, 2020, 00:51 Ralph Goers >> wrote: >>>> >>

Re: Log4j 2.14.0 release status

> Is wrong... darn. >> >> Gary >> >>> On Sun, Nov 1, 2020, 08:05 Gary Gregory wrote: >>> >>> Very odd indeed, the public (non-snapshot) repository is full of snapshots: >>> >>> >>> https://repository.apache.org/content

Re: Log4j 2.14.0 release status

e for the doap plugin. Ralph > On Nov 1, 2020, at 10:21 AM, Matt Sicker wrote: > > Well at least it's not an ongoing problem with the new setup. I wonder > how that got there... > > On Sun, 1 Nov 2020 at 10:45, Ralph Goers wrote: >> >> Yes, Nexus indicates t

Re: Log4j 2.14.0 release status

v 2, 2020, at 9:13 AM, Ralph Goers wrote: > > Infra removed all the snapshots and I validated that the generated doap file > no longer has the snapshots in it, but the plugin is still failing with > "java.lang.IllegalArgumentException: Invalid version number: Version number

Dependabot

If you are going to apply the PRs dependabot generates then you need to make sure the appropriate checks are done. Dependabot upgraded the maven checkstyle plugin. This plugin is used in the mvn site build, but I believe our builds don’t normally run that so it looked like everything was ok. Ho

Fwd: [CI][UNSTABLE] Logging/log4j/release-2.x#129 has test failures

These failures are on Windows and look like perhaps they are errors trying to cleanup files. The errors say they can’t be deleted because they are in use. Although these should be fixed I don’t consider them blockers for a release. Ralph > Begin forwarded message: > > From: "Mr. Jenkins" >

Re: Escaping dollar ($) character in .adoc.vm

Yes, I have added it to my local copy and am running the site build (for the nth time) in preparation for the release. Ralph > On Nov 6, 2020, at 8:40 AM, Matt Sicker wrote: > > There's supposed to be a variable declaration at the top of the > velocity file to define the dollar variable to '$

Re: [CI][UNSTABLE] Logging/log4j/master#175 has test failures

And there are failures on both Windows and Linux. Ralph > On Nov 6, 2020, at 8:42 AM, Matt Sicker wrote: > > Uh oh, those are some new ones. > > On Fri, 6 Nov 2020 at 08:14, Mr. Jenkins > wrote: > >> *BUILD UNSTABLE* >> Build URL >> https://ci-builds.apache.org/job/Logging/job/log4j/job/mast

[VOTE] Release Log4j 2.14.0-rc1

This is a vote to release Log4j 2.14.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: Chainsaw update

Great to hear from you again! I don’t know if you saw it but there is a Chainsaw related email on Feb 12 of this year in the private list that you should take a look at if you are planning on doing some work on Chainsaw. Ralph > On Nov 6, 2020, at 5:57 PM, Scott Deboy wrote: > > Hey all, >

TestConfigurator error

/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac" > > Any thoughts? > > As much of the build log from the console: https://pastebin.com/xQsttBna &

Re: [VOTE] Release Log4j 2.14.0-rc1

Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T12:39:06-07:00) Maven home: /opt/maven/maven Java version: 1.8.0_202, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: &q

Minimum Java version for Log4j 2 3.0?

One of the goals for 3.0 is to have it fully support the Java Platform Module System. Currently, we are required to have a java 8 project and a java 9 project and merge them. If we say that 3.0 will only support Java 11+ then we can get rid of these extra projects and add module-info.java to al

Re: Chainsaw update

gt; >>>>> On Sat, 7 Nov 2020 at 11:12, Scott Deboy >>> wrote: >>>>>> >>>>>> I assume reverse-connect is still fine (SocketHubAppender/Receiver), >>>>>> as Chainsaw is being configured to reach a specific (assumed tr

Re: TestConfigurator error

;> 2020-11-07 19:47:34,171 main ERROR Unknown object "Root" of type >> org.apache.logging.log4j.core.config.LoggerConfig is ignored: try nesting >> it inside one of: ["Appenders", "Loggers", "Properties", "Scripts", >> "CustomLeve

Re: [VOTE] Release Log4j 2.14.0-rc1

ry/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre >> Default locale: en_US, platform encoding: UTF-8 >> OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac" >> >> Any thoughts? >> >> As mu

Re: Minimum Java version for Log4j 2 3.0?

ompromise in > https://issues.apache.org/jira/browse/LOG4J2-2922 > > Depending on how that works out, it may still be possible to support > Java 8, or it would potentially allow for 2.x and 3.x to maintain some > build compatibility to make it easier to backport anything. > >

Re: Minimum Java version for Log4j 2 3.0?

I should add to this that since I plan to add module-info files for every Log4j module this is going to mean creating java9 modules for every module we currently have. I really don’t want to do that. Ralph > On Nov 8, 2020, at 10:26 PM, Ralph Goers wrote: > > I’ve just spent m

Re: [VOTE] Release Log4j 2.14.0-rc1

them, then that's a problem and a self-inflicted >> wound IMO. >> >> Now I must apologize for not digging into this new test framework now to >> suss out exactly what is going on, but I am hoping someone can help me >> understand what's going on here. >

[RESULT][VOTE] Release Log4j 2.14.0-rc1

This vote has passed with 3 binding +1 votes from Matt Sicker, Remko Popma and Ralph Goers, 1 binding +0 vote from Gary Gregory, and a +1 vote from Volkan Yazici. I will continue with the release process. Ralph

[ANNOUNCEMENT] Log4j 2.14.0 released

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

Identifying the set of events to be logged

FYI - https://www.ralphgoers.com/post/identifying-the-set-of-events-to-be-logged Ralph

Re: Opt in for JMX server?

I believe that will be a requirement in Master since JMX isn’t included in the base module. Ralph > On Nov 16, 2020, at 7:44 AM, Carter Kozak wrote: > > Sounds like a great idea to me. At work we use a different framework to > report metrics and generally disable jmx everywhere that allows us

Re: Review request for LOG4J2-2962

I’ll see if I can find time later tonight. Ralph > On Nov 17, 2020, at 2:59 PM, Volkan Yazıcı wrote: > > In LOG4J2-2962, Magnus Kvalheim requests a functionality for the "map" > resolver similar to the one in "mdc". Guess what? They both operate on > `ReadOnlyStringMap`s and there goes my MR: >

Re: Issue with TimeAndSizeRollingAppender log4j version 1.2.16

Log4j 1.2.x reached end-of-life in August of 2015. It really hasn’t been supported for at least 6 years and none of the current committers have any recent familiarity with it. I would suggest you upgrade to Log4j 2. You might try asking on Stackoverflow and see if you have better luck. Ralph >

Re: [log4j] Release log4j-tools

There is a Jira issue to do that but as far as I know the Security bug was never addressed in that code. In a quick glance at it I still see it supporting Java serialized objects without any kind of whitelisting. I don’t see anything in that repo besides the log server and I wouldn’t want to rel

Log4PHP status

Most of the committers for Log4PHP have gone on to other things. The few that are still participating in the Logging Services PMC have indicated that they are not working on the project any more. As such, no one has been maintaining the project for quite a while. The PMC has discussed moving the

Re: unable to build from source

You are making progress! I saw those same errors in one of our automated builds the other day. I am not sure what the problem is but haven’t looked into it yet. Ralph > On Dec 8, 2020, at 9:23 AM, Joseph Tsai wrote: > > I kinda inferred that from reading the mvnw script when Volkan directed me

[VOTE] Move Log4PHP to dormant status

I started a discussion several days ago regarding moving Log4PHP to dormant status and have gotten no feedback. Given there has been no development activity in years and there is no one actively working on the project it seems it should be moved to dormant status. This vote will be open for 72h

Log4Go

The company I work for has started using Go for some of the middleware components we are developing. I have looked at several logging frameworks for Go and have not been impressed by any of them. As such, I am considering starting a project here. The major goals of this would be: Use an externa

Re: [log4j] Release log4j-tools

's servers uses through ObjectInputStreamLogEventBridge. > > Gary > > On Thu, Dec 3, 2020 at 10:33 AM Ralph Goers > wrote: > >> There is a Jira issue to do that but as far as I know the Security bug was >> never addressed in that code. In a quick glance at it I

Re: [log4j] Release log4j-tools

020, at 1:50 PM, Gary Gregory wrote: > > I think the log4j-tools version should be set to 2.14.0 for a RC to match > the release of log4j. Thoughts? > > Gary > > On Thu, Dec 10, 2020, 15:45 Ralph Goers wrote: > >> OK. Then I guess I forgot since it has been so lon

Re: [VOTE] Move Log4PHP to dormant status

My +1 Ralph > On Dec 9, 2020, at 2:20 PM, Ralph Goers wrote: > > I started a discussion several days ago regarding moving Log4PHP to dormant > status and have gotten no feedback. Given there has been no development > activity in years and there is no one actively working on

[RESULT][VOTE] Move Log4PHP to dormant status

This vote has passed with 8 binding +1 votes. I will make the appropriate site modifications and ask infra to lock down the issue tracker. Ralph

Re: [General] Logging Wiki

What you do with the wiki is totally up to whoever is working on log4cxx. Ralph > On Dec 26, 2020, at 9:04 AM, Robert Middleton wrote: > > One thing that I've been doing over the holidays is to work more on > the log4cxx website migration to Doxygen instead of Maven, and I came > across the log

Re: [log4cxx] Site / Release?

If you aren’t already, just be aware that the web site is actually deployed from https://github.com/apache/logging-log4cxx-site following the instructions at https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Sites in the section titled "Updating Logging Servi

Re: [log4cxx] Site / Release?

You should not need to run the build to generate the web site on multiple platforms and I would think that the build to generate web site documentation would be separate from performing the release build. That said, I haven’t looked at the log4cxx build so I am not at all familiar with it. Ral

Re: Deleting log4j-layout-jackson* modules from master

Volkan, I am fine with deleting those modules however that would require that you make sure that you replace the existing Layouts with ones that use JsonTemplateLayout templates, take the same configuration parameters and produce the same results. In other words, when people move from 2.x to 3.

<    5   6   7   8   9   10   11   12   13   14   >