Fwd: log4net security audit publishing

In case anyone is interested - it's nice to have some positive feedback from a security researcher. Good work, Jan. There's a pdf report with the original mail which is too large to send on this list. If anyone wants it, please let me know. -d --- Forwarded message --- From: Derek Zimmer de

Fwd: [VOTE] Release Apache Log4net 3.1.0

Forwarded Message Subject: Re: [VOTE] Release Apache Log4net 3.1.0 Date: Mon, 12 May 2025 10:34:16 +0200 From: Davyd McColl To: Jan Friedrich Apologies, I replied directly instead of to the mailing list In addition to the below, I'd recommend switching the windows verif

Fwd: [VOTE] Release Apache Log4net 3.1.0

Forwarded Message Subject: Re: [VOTE] Release Apache Log4net 3.1.0 Date: Mon, 12 May 2025 10:21:44 +0200 From: Davyd McColl To: Jan Friedrich +1: Current testing issues as per this thread aside, verification worked fine on windows and linux @Jan, I've ported your verify

Fwd: logging-log4j2.git: Error while running github feature from 2.x:.asf.yaml

Could you help us to understand this `.asf.yaml` failure, please? The pointed list entry *is* an uppercase string. P.S. See the docs on JIRA auto-linking

Fwd: [VOTE] Release Apache Log4net 3.0.3

This was the +1 from Davyd. Jan This is a forwarded message From: Davyd McColl To: Jan Friedrich Date: Tuesday, November 5, 2024, 8:54:35 AM Subject: [VOTE] Release Apache Log4net 3.0.3 ===8<==Original message text=== +1 tests all pass, sigs all verified -d On 2024-11

Fwd:

Apologies, I responded directly to Volkan instead of the list ): -d Forwarded Message Subject:Re: Date: Tue, 13 Feb 2024 12:00:05 +0200 From: Davyd McColl To: Volkan Yazıcı I'd really like to chuck JIRA in a lake of fire and watch it burn slowly /2c On

Fwd: Using the Log4j 1.2 bridge.

Hi All and Piotr mostly (since you did the 2.x code in Commons Logging), [ Background: My reply https://lists.apache.org/thread/rcxkfffg9pfj9662d1fxlyo4l8cv2yyq to the post https://lists.apache.org/thread/w5yq2locvdt8yhf8k9075vgjg1kw5569 ] In my branch https://github.com/garydgregory/commons-log

Fwd: JDK 21 Is Now GA, a New VS Code Extension, and an Annotation Processing Heads-up

Snippet from the JDK 21 announcement email that pertains to us. While the annotation processor was initially developed to try to be implicit and magic, as we’ve seen both in our build and in IDEs, annotation processing is typically either disabled by default (in IDEs) or sometimes requires manua

Fwd: Shared GitHub actions

Something that may be relevant as we split up repos more and have more actions defined. > Begin forwarded message: > > From: Slawomir Jaranowski > Subject: Shared GitHub actions > Date: August 19, 2023 at 10:17:58 AM CDT > To: Commons Developers List > Reply-To: "Commons Developers List" > Li

Fwd: [DISCUSS] Quo Vadis Maven Site

Just FYI from the Maven list regarding site generation. -- Forwarded message - From: Tamás Cservenák Date: Wed, Nov 16, 2022, 05:19 Subject: [DISCUSS] Quo Vadis Maven Site To: Maven Developers List Howdy, This is really just a brainstorming thread I'd like to spin, regarding M

Fwd: [ANNOUNCE] Changes to Jira Account Creation (issues.a.o/jira)

This is relevant to potentially switching to GitHub issues. Begin forwarded message: > From: fluxo > Date: October 21, 2022 at 20:02:01 CDT > To: annou...@infra.apache.org > Subject: [ANNOUNCE] Changes to Jira Account Creation (issues.a.o/jira) > Reply-To: us...@infra.apache.org > > Hello PMC

Fwd: [apache/logging-log4j2] Run failed: build - master (1be6c1e)

What’s going on with CI now? I’m not impressed by a random Windows failure breaking the entire build, especially one that’s apparently been failing for a while apparently. Dependabot?? — Matt Sicker > Begin forwarded message: > > From: Matt Sicker > Subject: [apache/logging-log4j2] Run failed:

Fwd: ci-builds all 3.6TB disk is full!

Hi All, Looks like our Looging project is using too much space, almost 6 GB in the CI system. Does anyone here know how to clean this up and prevent it from happening? Gary -- Forwarded message - From: Gavin McDonald Date: Wed, Apr 20, 2022, 03:27 Subject: ci-builds all 3.6TB dis

Fwd: [REMINDER]: Submissions Open for Community Track at ApacheCon New Orleans

I don’t think I’ll be able to submit a talk this year unfortunately (still going through some OSPO approval process for Log4j in general), but I’ll certainly be at ApacheCon this year. I highly encourage contributors here to submit a talk proposal. There’s a couple relevant tracks such as perfor

Fwd: [NOTICE] Introducing GitHub Actions build status notification for git repositories.

In a nutshell, we can configure `.asf.yaml` to email build status. I want to enable this feature on both `release-2.x` and `master` and point it to ` notificati...@logging.apache.org`. Objections? -- Forwarded message - From: Daniel Gruno Date: Sat, Mar 26, 2022 at 9:58 PM Subject

Fwd: [GitHub] [logging-log4j2] ppkarwasz merged pull request #767: Provide a uniform Log4j 1.x message factory

Hi Piotr and welcome aboard. I usually update changes.xml but not in a PR, we generate the release notes from changes.xml. Gary -- Forwarded message - From: GitBox Date: Fri, Mar 4, 2022 at 2:57 PM Subject: [GitHub] [logging-log4j2] ppkarwasz merged pull request #767: Provide a

Fwd: [jira] [Resolved] (ZOOKEEPER-2342) Migrate to Log4J 2.

FYI -- Forwarded message - From: Chris Nauroth (Jira) Date: Wed, Feb 9, 2022, 14:11 Subject: [jira] [Resolved] (ZOOKEEPER-2342) Migrate to Log4J 2. To: [ https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Fwd: [apache/logging-log4j2] Bump tomcat-catalina from 8.5.20 to 10.0.14 (PR #662)

This Tomcat upgrade looks legit to me. Nevertheless, I'd appreciate it if a Tomcat veteran could weigh in. -- Forwarded message - From: knoxyz Date: Thu, Jan 20, 2022 at 3:28 PM Subject: Re: [apache/logging-log4j2] Bump tomcat-catalina from 8.5.20 to 10.0.14 (PR #662) To: apache/l

Fwd: Cannot find doap file: https://logging.apache.org/log4j/2.x/doap_log4j.rdf

FYI -- Forwarded message - From: Projects Date: Wed, 15 Dec 2021 at 02:00 Subject: Cannot find doap file: https://logging.apache.org/log4j/2.x/doap_log4j.rdf To: Site Development URL: https://logging.apache.org/log4j/2.x/doap_log4j.rdf HTTP Error 404: Not Found Source: https://

Fwd: git master and Serializable

I think we should drop implementing Serializable on anything for 3.0.0. A la Effective Java #85. Gary

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

Hi asf-staging branch merged into asf-site and I can see the latest release notes are up Apologies again for missing this. -d On 2021/11/05 16:31:41, Davyd McColl wrote: Apologies - staging docs have not been set live ): I'll have a look at it now -d On 2021/11/05 16:24:55, Volkan Yazıcı w

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

Apologies - staging docs have not been set live ): I'll have a look at it now -d On 2021/11/05 16:24:55, Volkan Yazıcı wrote: I think this message is best suited for this mailing list. Would anybody from the log4net crew mind addressing the request of John Bigler, please? -- Forwarded

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

I think this message is best suited for this mailing list. Would anybody from the log4net crew mind addressing the request of John Bigler, please? -- Forwarded message - From: NuGet Gallery Date: Thu, Nov 4, 2021 at 5:50 PM Subject: [NuGet Gallery] Message for owners of the packag

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

Recently added SocketAppenderReconnectTest is failing on Windows. Will look into it... -- Forwarded message - From: Mr. Jenkins Date: Mon, 25 Oct 2021, 00:05 Subject: [CI][UNSTABLE] Logging/log4j/release-2.x#375 has test failures To: *BUILD UNSTABLE* Build URL https://ci-builds

Fwd: Apache Log4j is part of the Mars 2020 Helicopter mission

-- Forwarded message - From: Gary Gregory Date: Fri, Jun 4, 2021, 11:27 Subject: Apache Log4j is part of the Mars 2020 Helicopter mission To: Log4J Developers List , Sally Khudairi < sallykhuda...@yahoo.com> Hi Sally and All, My GitHub profile was adorned with a new badge today:

Fwd: [apache/logging-log4j2] MapMessage put methods should not mandate String values (#477)

Hello, Adding non-String-typed value support to MapMessage was also something on my radar too. But this PR replacing String with Object in two lines seems too good to be true to me. Does anybody mind taking a second look at this, please? Kind regards. -- Forwarded message - From:

Fwd: [apache/logging-log4j2] ensure EncodingPatternConverter#handlesThrowable is implemented (#473)

The patch "seems" legit to me, but I don't know much about pattern converters. It is a pretty innocent looking small change – would anybody more knowledgeable about the subject mind checking the PR, please? -- Forwarded message - From: Romain Manni-Bucau Date: Tue, Mar 9, 2021 at

Fwd: Log4j JSON layout template Uris enum

Hi all, Why is this an enum and not a class? Gary

Re: Fwd: Opt in for JMX server?

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 to do so. -ck On Mon, Nov 16, 2020, at 09:39, Gary Gregory wrote: > Hi All, > > I am starting to think that registering JMX MBeans after setting a config >

Fwd: Opt in for JMX server?

Hi All, I am starting to think that registering JMX MBeans after setting a config from the Core's logger context should be opt in and not done always. This would make startup (a little?) faster and "safer" since opening up JMX could be considered a security issue. At least we have a global opt o

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: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

Dear Santosh, please see the answer to Your request below. Please note that Apache product discussions happen on mailing lists, in this case it is dev@logging.apache.org. NuGet messages are not an ideal way to communicate because they reach only a limited subset of the community. Warm regards, Do

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

Hi Dominik iirc, this was fixed in 2.0.11. 2.0.12, with another fix for current user name on !win32, is waiting on one more +1 vote for release. -d On October 23, 2020 18:05:18 Dominik Psenner wrote: See the message below. -- Sent from my phone. -- Forwarded message - Fro

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

See the message below. -- Sent from my phone. -- Forwarded message - From: NuGet Gallery Date: Fri, Oct 23, 2020, 07:51 Subject: [NuGet Gallery] Message for owners of the package 'log4net' To: *User santoshkallatti > sends the following message to the owners of Package 'log4net

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

Why does this say "No new revisions were added by this update"? This has been going on any time I push commits to master, though it's not happening when I push them to release-2.x. I only noticed this now because I hadn't backported this at the same time. -- Forwarded message - Fro

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

Ok, I've found the culprit -- there's a lot of assembly version sources which mention 2.0.9 -- and I'm not entirely sure why some of them are in this project (AssemblyVersionInfo.cpp, AssemblyVersionInfo.js, AssemblyVersionInfo.vb). And there are two files which set up assembly version informati

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

hm, that's not great ): I'll investigate. Thanks for letting me know! -d On 2020/09/18 13:05:58, Dominik Psenner wrote: See the message below. Apparently something went wrong during the last release. -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. -- For

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

See the message below. Apparently something went wrong during the last release. -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. -- Forwarded message - From: NuGet Gallery Date: Fri, Sep 18, 2020, 12:10 Subject: [NuGet Gallery] Message for owners of

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

This reflects my impression that the volume of individuals that do not know the mechanics of the mailing lists has increased. I observe that with the increased number of messages that need to be moderated. Many come from individuals that are not subscribes. Others come from individuals that send me

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

True that, but I tried to initiate a vote the other day from my work mail by mistake and the message was bounced, so I'm not sure what rules apply to this list. If it's fairly open, it might be a plan to update the associated email address on nuget to the dev list. -d On September 8, 2020 19

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

That's this dev list! Though if we need a separate mailing list, we can always create more. On Tue, 8 Sep 2020 at 11:54, Davyd McColl wrote: > > What if there was another Apache email address that messages were sent to, > and multiple people could observe that account? I don't mind being one of >

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

What if there was another Apache email address that messages were sent to, and multiple people could observe that account? I don't mind being one of the lucky ones if it will help (: -d On September 8, 2020 17:47:57 Matt Sicker wrote: The main problem with sending nuget info to the PMC is

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

The main problem with sending nuget info to the PMC is that nobody in the PMC are working on log4net besides validating releases ;) On Tue, 8 Sep 2020 at 04:37, Dominik Psenner wrote: > > In the past security vulnerabilities were reported via nuget and it is not > a good idea to publish those in

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

In the past security vulnerabilities were reported via nuget and it is not a good idea to publish those in an automated way. I suggest to update the nuget project documentation and prominently point to our mailing lists and discourage the communication via nuget. Users may continue sending message

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

Ralph I understand that the emails provide a bit of workload, and I'm trying to figure out a solution to help everyone -- obviously there are people who submit mails (and wonder where they went) and people who have to handle those mails. We use Trello at work and have built our own custom solut

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

Hi Ralph I'll investigate this today. I'd like more information, particularly configuration and, eg if the ado.net appender is used, table structures. Joseph, please open a ticket at https://issues.apache.org/jira/browse/LOG4NET to help me track this. -d On September 7, 2020 23:35:12 Ral

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

Fwd: [IMPORTANT] - Migration to ci-builds.a.o

Here’s the answer to my previous forward. I can look into this to make sure our builds are good there. -- Forwarded message - From: Gavin McDonald Date: Thu, Jul 16, 2020 at 11:33 Subject: [IMPORTANT] - Migration to ci-builds.a.o To: builds Hi All, This NOTICE is for everyone

Fwd: [IMPORTANT] - 2 more HADOOP nodes migrated over to ci-hadoop

Do we need to look into requesting our own CloudBees Managed Master like the Hadoop one? From what I remember, many of the nodes that can run our build are these H-nodes which seem to be moving. -- Forwarded message - From: Gavin McDonald Date: Thu, 16 Jul 2020 at 04:33 Subject: [

Fwd: svn commit: r39338 - in /release/logging/log4j/scala: 11.0/ 12.0/

Somehow, these file name _still_ don't match the ones on the download page. Ugh! Will need to fix before committing the site and announcing the release. -- Forwarded message - From: Date: Sat, 9 May 2020 at 12:53 Subject: svn commit: r39338 - in /release/logging/log4j/scala: 11.0/

Fwd: [slf4j-user] Combined logging and throwing question

Potentially useful API update to look at here. Some sort of Logger that throws an exception with the log message instead? -- Forwarded message - From: Norbert Kiesel Date: Wed, 6 May 2020 at 12:59 Subject: [slf4j-user] Combined logging and throwing question To: User list for the s

Fwd: [logging-log4j-scala] annotated tag v12.0-rc3 created (now 77da542)

I have to burn this release candidate as the release instructions were incorrect. Also, despite this email's "Reply-To" field being dev@, Gmail _insists_ on making the Reply button reply to the commits mailing list. -- Forwarded message - From: Date: Sun, 3 May 2020 at 11:01 Subje

Fwd: [log4j] InitTest fails in release-2.x

-- Forwarded message - From: Gary Gregory Date: Wed, Apr 29, 2020, 18:33 Subject: [log4j] InitTest fails in release-2.x To: Commons Developers List I always get this failure in release-2.x and 'mvn clean install -V': [INFO] Running org.apache.logging.log4j.core.util.InitTest Ti

Fwd: Google Summer of Code 2020 Mentor Registration

Given some project ideas from the community here, I might be able to help mentor or co-mentor a project here in log4j. Any suggestions? -- Forwarded message - From: Maxim Solodovnik Date: Thu, Feb 27, 2020 at 20:08 Subject: Google Summer of Code 2020 Mentor Registration To: Dea

Fwd: [apache/logging-log4cxx] Replace ant build with cmake (#14)

Hi All, I have done everything I can think of prepare https://github.com/apache/logging-log4cxx/pull/14 for inclusion in the repository. Please review. On Sat, Feb 8, 2020 at 3:33 AM Matt Sicker wrote: > *@jvz* commented on this pull request. > -- > > In src/site/ap

Fwd: [logging-log4j2] branch release-2.x updated: Add jdk8 to toolchain

For some reason, the Reply-To address is being ignored by Gmail for this message. Anyways, I can't figure out which combination of JDKs to use for release-2.x. The closest combo I found to work was jdk8+jdk11, but then there was a unit test failure in the YAML config which is likely related to jdk7

Fwd: svn commit: r1866249 - /infrastructure/site/trunk/content/legal/resolved.mdtext

Based on this clarification, we do not need to remove the maven wrapper jar from our source distributions. I brought this up in the last release vote, so I'm noting here that it's no longer an issue. -- Forwarded message - From: Date: Sun, 1 Sep 2019 at 21:56 Subject: svn commit:

Re: Fwd: Travel Assistance for ApacheCon NA Las Vegas 2019 now open.

My talk wasn't accepted, and based on the schedule, it would be rather hard to argue that this conference is work-related, so I won't be able to attend this year unfortunately. On Sun, 30 Jun 2019 at 11:15, Carter Kozak wrote: > > Hi Folks, > > I've registered to attend ApacheCon Vegas, hoping to

Re: Fwd: Travel Assistance for ApacheCon NA Las Vegas 2019 now open.

Hi Folks, I've registered to attend ApacheCon Vegas, hoping to see you there! -ck On Sun, May 19, 2019, at 14:38, Matt Sicker wrote: > Hello everyone! This year, I know of at least two submissions to > ApacheCon Las Vegas that are related to Log4j. While the schedule > hasn't been confirmed or p

Fwd: MODERATE for annou...@apache.org

For future reference, the download page does not meet requirements. https://www.apache.org/dev/release-distribution#download-links SHA1 is no longer considered a reliable checksum. Please convert to use SHA256 and/or SHA512 for future releases. The requirements are SHOULD NOT for SHA1 solely be

Fwd: Travel Assistance for ApacheCon NA Las Vegas 2019 now open.

Hello everyone! This year, I know of at least two submissions to ApacheCon Las Vegas that are related to Log4j. While the schedule hasn't been confirmed or posted yet, TAC has opened up applications now to be able to go to ApacheCon. If you'd love to come to ApacheCon this year but are financially

Fwd: [logging-log4j2] branch release-2.x updated: Enhance direct write test. Add new OnStartup test

Hi, I think the Jenkins build failures are related to this commit :-( Gary -- Forwarded message - From: Date: Sun, Dec 9, 2018 at 10:23 AM Subject: [logging-log4j2] branch release-2.x updated: Enhance direct write test. Add new OnStartup test To: comm...@logging.apache.org Th

Fwd: [4/4] httpcomponents-core git commit: Added openjdk10 to Travis-CI build matrix

I think we can skip Java 9 and 10 and instead test Java 11. Gary -- Forwarded message - From: Date: Fri, Dec 7, 2018 at 8:53 AM Subject: [4/4] httpcomponents-core git commit: Added openjdk10 to Travis-CI build matrix To: Added openjdk10 to Travis-CI build matrix Project: htt

Fwd: Jenkins build became unstable: Log4j 2 2.x #3753

Is this failure related to the recent file close issue in the tests? Gary -- Forwarded message - From: Apache Jenkins Server Date: Sat, Dec 1, 2018 at 3:53 PM Subject: Jenkins build became unstable: Log4j 2 2.x #3753 To: See

Fwd: log4net / .ner core 2.1 / SmtpAppender

Apparently I forgot to add dev at logging dot apache dot org to the recipients. Here comes the last message as a forward. -- Forwarded message - From: Dominik Psenner Date: Mon, 22 Oct 2018 at 13:57 Subject: Re: log4net / .ner core 2.1 / SmtpAppender To: Michael Karmazin (public)

Fwd: Java 11 / JDK 11: General Availability

JDK 11, the reference implementation of Java 11 and the first long-term support release produced under the six-month rapid-cadence release model [1][2], is now Generally Available. We've identified no P1 bugs since we promoted build 28 over four weeks ago so that’s the official GA release, ready

Fwd: [ANNOUNCE] Apache Log4j 2.11.1 released

Blogged: https://blogs.apache.org/logging/entry/log4j-2-11-1-released Please share on social media. On Tue, Jul 31, 2018 at 2:38 PM, Ralph Goers wrote: > > The Apache Log4j 2 team is pleased to announce the Log4j 2.11.1 release! > > Apache Log4j is a well known framework for logging application

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

On 2018-07-19 22:17, sean.co...@gmail.com wrote: Dominik, There are a number of issues in your tracker that are directly related to sticking with NetStandard 1.3. That was an early release and must have been painful to try to do a full implementation of Log4Net. 2 issues dear to me are Va

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

Dominik, There are a number of issues in your tracker that are directly related to sticking with NetStandard 1.3. That was an early release and must have been painful to try to do a full implementation of Log4Net. 2 issues dear to me are Variable Expansion (Environment.GetEnvironmentVariable

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

Hi Bart, thanks for your interest in log4net. There's an issue for this and we have an open pull request that adds this target. We have however no plan yet of when this should happen. By targeting log4net against netstandard-1.3 it can be referenced from that netstandard and any netstandard f

Fwd: StatusLogger contention?

Hi All: I get this garbled StatusLogger output when running Mongo tests from Maven: [INFO] Running org.apache.logging.log4j.mongodb3.MongoDbMapMessageTest ERREERORRROOR StatusLogger No Log4j 2 configuration file founRd. UsingR defau StatusLogger No Log4j 2 configuration file found.lt configuratio

Fwd: Build failed in Jenkins: Log4j 2 2.x #3461

How do we fix this? Gary -- Forwarded message -- From: Apache Jenkins Server Date: Thu, Apr 26, 2018 at 11:58 AM Subject: Build failed in Jenkins: Log4j 2 2.x #3461 To: notificati...@logging.apache.org See -

Fwd: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf

Please fix this. -- Forwarded message -- From: Projects Date: 12 April 2018 at 03:00 Subject: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf To: Site Development WARN: invalid asfext:pmc 'https://logging.

Fwd: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf

As the subject says: the asfext:pmc value is incorrect; it must point to a PMC not a release. -- Forwarded message -- From: Projects Date: 10 April 2018 at 03:00 Subject: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap

Fwd: [logging-log4j2] Git Push Summary

We need another Jenkins build for this. We should also change the POM version in git master to avoid mixing things up. Gary -- Forwarded message -- From: Date: Jan 30, 2018 06:51 Subject: [logging-log4j2] Git Push Summary To: Cc: Repository: logging-log4j2 > Updated Branches: >

Fwd: LOG4J2-2062 Error in Travis Job

Hi Devs, I have created ticket https://issues.apache.org/jira/browse/LOG4J2-2062 in order to improve the KafkaAppender with the possibility of including a Key to every message sent to a Kafka topic and I have run mvn clean verify as stated in the Contributing page with all the tests in the log4j-c

Fwd: log4j-to-slf4j

Well, SLF4J recently changed the binding mechanism with 1.8 in order to comply with Java 9. It isn’t likely to do it again any time soon. What we would “solve” is that now it is log4j-api -> log4j-to-slf4j -> slf4j-api -> logging implementation. With this change it would be log4j-api -> log4j

Fwd: Build failed in Jenkins: Log4j 2.x #3052

Frak! What could cause the JConsolePlugin class to not be found? Gary -- Forwarded message -- From: Apache Jenkins Server Date: Mon, Sep 11, 2017 at 2:17 PM Subject: Build failed in Jenkins: Log4j 2.x #3052 To: dev@logging.apache.org See

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

A local build worked for me (mvn clean install), this looks a Nexus issue maybe. Gary -- Forwarded message -- From: Apache Jenkins Server Date: Mon, Sep 11, 2017 at 12:36 PM Subject: Build failed in Jenkins: Log4j 2.x #3051 To: dev@logging.apache.org See

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

Hi, Chris just resolved our infra ticket regarding .net frameworks on the windows nodes. This is a summary of the outcome: > Chris Thistlethwaite resolved INFRA-14645. > -- >Resolution: Fixed >> 1. We have observed that none of the windows nodes appear

Re: Fwd: nant on debian stretch

over at sourceforge. > > Hope this helps, > Ryan > > On Aug 18, 2017 8:44 AM, "Dominik Psenner" wrote: > > I just sent the following to the nant-developers mailing list. > > -- Forwarded message -- > From: Dominik Psenner > Date: 2017-0

Re: Fwd: nant on debian stretch

one. Best bet is to use one of the prebuilt tarballs over at sourceforge. Hope this helps, Ryan On Aug 18, 2017 8:44 AM, "Dominik Psenner" wrote: I just sent the following to the nant-developers mailing list. -- Forwarded message -- From: Dominik Psenner Date: 2017-08-1

Fwd: nant on debian stretch

I just sent the following to the nant-developers mailing list. -- Forwarded message -- From: Dominik Psenner Date: 2017-08-18 17:18 GMT+02:00 Subject: Fwd: nant on debian stretch To: nant-develop...@lists.sourceforge.net Hi there, I'm reaching out to you wearing the hat o

Fwd: Jenkins build became unstable: Log4j 2.x #2924

FWIW, It _seems_ that errors like https://builds.apache.org/job/Log4j%202.x/org.apache.logging.log4j$log4j-core/2924/testReport/junit/org.apache.logging.log4j.core.appender.rolling/RollingAppenderDirectWriteWithReconfigureTest/testRollingFileAppenderWithReconfigure/ happen when the machine is bus

Fwd: Review Request 61010: HIVE-17128 Operation Logging leaks file descriptors as the log4j Appender is never closed

In the Apache Hive message below, you'll see mention of using reflection to implement something I thought we already supported: closing files file that are dynamically created. Any thoughts on how set get Hive to use Log4j in a safer manner? Gary -- Forwarded message -- From: Aih

Fwd: Build failed in Jenkins: Log4j 2.x #2877

There seems to be a problem with Jenkins on a daily bases. PITA. Just frustrated... Gary -- Forwarded message -- From: Apache Jenkins Server Date: Fri, Jul 7, 2017 at 2:55 PM Subject: Build failed in Jenkins: Log4j 2.x #2877 To: dev@logging.apache.org See

Fwd: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #72

This just happened now for the first time. Hasn't happened before and might be gone with a rebuild. Still, has anyone seen this (or something similar) before? [csc] Compiling 226 files to '/home/jenkins/jenkins-slave/workspace/log4net_feature_cd-pipeline-76KUCPODUF6LCE45226EBUR4GNVLYPMYVC23Z

Fwd: [6/6] [text] Merge branch 'travis-ibmjdk8' of https://github.com/ameyjadiye/commons-text

Hi Rob, Thank you for pushing this through. Would you consider doing the same for the few other Travis builds we have in Commons? Thank you, Gary -- Forwarded message -- From: Date: Mon, Jun 12, 2017 at 4:58 AM Subject: [6/6] [text] Merge branch 'travis-ibmjdk8' of https://gith

Fwd: failure notice

[Wrong ML before] Hi All, I am adding the following methods to the MapMessage class: org.apache.logging.log4j.message.MapMessage.forEach(BiConsumer) org.apache.logging.log4j.message.MapMessage.forEach(TriConsumer, S) that will simply delegate to the underlying map. This will avoid call sites ca

Fwd: JSON License and Apache Projects

So how much does this affect us? Is Jackson affected? Is JSON even supportable in an open source fashion? -- Forwarded message -- From: Chris Mattmann Date: 23 May 2017 at 12:11 Subject: Fwd: JSON License and Apache Projects To: legal-disc...@apache.org Dear PMCs@, Hi! As the

Fwd: [ANNOUNCEMENT] HttpComponents Client 5.0 alpha2 released

FYI, this alpha uses Log4j 2. Gary From: Oleg Kalnichevski Sent: Thursday, May 11, 2017 5:54:27 AM To: annou...@apache.org; priv...@hc.apache.org; d...@hc.apache.org; httpclient-us...@hc.apache.org Subject: [ANNOUNCEMENT] HttpComponents Client 5.0 alpha2 release

Fwd: The Apache Software Foundation Welcomes 64 New Members

Congrats Matt on your Apache Membership! Gary From: Sally Khudairi Sent: Wednesday, May 3, 2017 11:41:34 AM To: Apache Announce List Subject: The Apache Software Foundation Welcomes 64 New Members [this announcement is available online at https://s.apache.org/2

Fwd: WARN Unable to instantiate org.fusesource.jansi.WindowsAnsiOutputStream

Hi All, It seems I am seeing: WARN Unable to instantiate org.fusesource.jansi.WindowsAnsiOutputStream A lot from Eclipse, Maven and Bamboo when I should not since jansi is on my CP. Any thoughts? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Se

Fwd: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#74)

Nice batch of comments, Matt. Gary -- Forwarded message -- From: Matt Sicker Date: Mon, Apr 24, 2017 at 1:14 PM Subject: Re: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#74) To: apache/logging-log4j2 Cc: Gary Gregory ,

Fwd: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#73)

Should this should go into a new module log4j-lucene? Gary -- Forwarded message -- From: liyujue Date: Wed, Apr 19, 2017 at 12:18 AM Subject: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#73) To: apache/logging-log4j2 C

Fwd: Failed tests

Hi, sorry I can't look ATM, I am probably not going to be able to spend much time here until next week. Gary On Apr 10, 2017 7:15 AM, "Mikael Ståldal" wrote: > Maybe Gary can have a look? According to Git history, he added those tests. > > On Mon, Apr 10, 2017 at 4:06 PM, Matt Sicker wrote: >

Fwd: [2/2] logging-log4j2 git commit: LOG4J2-1880 Warn when a configuration file for an inactive ConfigurationFactory is found

Hi, I think it would help to say what it means for a CF to be inactive vs. active (and how to change that). Gary -- Forwarded message -- From: Date: Apr 12, 2017 8:26 AM Subject: [2/2] logging-log4j2 git commit: LOG4J2-1880 Warn when a configuration file for an inactive Configura

Fwd: org.apache.logging.log4j.core.config.Configurator.initialize(String, String)

This is a nice showcase for an Either data type similar to Optional, but with a value or an error. On 12 April 2017 at 00:41, Gary Gregory wrote: > The problem with the API as it is now is that I have no idea if the API > did what I asked it to do. It does initialize log4j all right but not in a