I thought this was recently discussed on @members, but now I can't find the
thread! I'm not even sure if it was on @members, which exemplifies the
scaling problem discussed on the list, among other issues: When you look at
PonyMail's UI, there are about 60 internal mailing lists under the '
apache.
tead of the throw then I could understand what you are saying.
>
> Ralph
>
>
> > On Oct 9, 2024, at 9:55 AM, Gary Gregory wrote:
> >
> > Hi Ralph,
> >
> > Thank you for taking a peek.
> >
> > I either did not explain myself clearly or in enough detail
Hi Ralph,
Thank you for taking a peek.
I either did not explain myself clearly or in enough detail as I don't feel
you fully grasped what I proposed ;-)
"Secondly, I don’t like that the only criteria it is able to use to
determine whether to throw an exception is the log level."
It is _not_ onl
Hi Volkan,
Thank you for your review.
Later, I would like to have our whole build check all tests for Hibernate
warnings. Today, I'm taking a first step. The second step is to have
another Maven module's tests perform this check.
Recasting the solution as a JUnit 5 extension is a good idea, but
FWIW, I don't think apache voting guidelines allow for "you can only vote a
certain way only if ..."
Gary
On Wed, Oct 2, 2024, 3:30 PM Christian Grobmeier
wrote:
> Hello everyone,
>
> We have discussed this in the past. I hope we can pick up a decent dev
> speed with Flume after we adopt it. I
Jan,
If the vote says 72 hours, you should wait 72 hours before counting votes
and releasing ;-)
Gary
On Fri, Sep 27, 2024, 3:43 AM Fred am Nil wrote:
> Hi,
>
> and here is my +1.
>
> With that the vote passed with 3 +1 votes from Davyd McColl, Christian
> Grobmeier and myself.
> I will contin
I expected to see SBOMs in the binary zip, CycloneDX and/or SPDX. Are
they missing? Did I not find them?
Gary
On Tue, Sep 24, 2024 at 3:13 PM Piotr P. Karwasz
wrote:
>
> This is a vote to release the Apache Log4j `2.24.1`.
>
> Website: https://logging.staged.apache.org/log4j/2.24.1/index.html
>
+1 passes on macOS, fails on Windows as usual (see GH issues).
I tested the src zip file.
- ASC file OK
- SHA-512 file OK
- `mvn clean verify` OK
Environment:
openjdk version "17.0.12" 2024-07-16
OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0
This proposal is two pages (on my phone)! I can't imagine counting lines
and walking through these steps, it's crazy making IMO. How would you count
lines anyway? From diff output?
I'd rather skip the bikeshedding and let devs create PRs when they think it
makes sense. IOW, when they want a review
I'm with Matt. It should be left at the discretion of the developer whether
a PR or straight commit is justified. I see no reason to throw sand in the
gears.
Gary
On Tue, Sep 17, 2024, 2:05 PM Matt Sicker wrote:
> I’m -1 on switching to RTC. Same reason as always. Losing momentum from
> waiting
Maybe we should talk about net vs. J separately?
Gary
On Tue, Sep 17, 2024, 10:53 AM Piotr P. Karwasz
wrote:
> Hi Ralph,
>
> On Tue, 17 Sept 2024 at 15:47, Ralph Goers
> wrote:
> >
> > Why? i.e. - what currently isn’t working?
>
> I merely wish to formalize what is already happening and set up
Ah, thank you.
Gary
On Mon, Sep 16, 2024, 9:50 AM Jan Friedrich wrote:
> Hi Gary,
>
> please see
> https://lists.apache.org/thread/v8kyxz7zdvp3cypo1506yflk3bbvysym
>
> I did not change the subject to [RESULT].
>
> Regards.
>
> Jan
>
> On 16 September 2024
I don't think I saw a [RESULT] message with a tally of the result.
Gary
On Sun, Sep 15, 2024 at 3:26 PM Davyd McColl wrote:
>
> Hi
>
> Apologies for the late response. FWIW, my +1 too.
>
> -d
>
>
> On 15 September 2024 20:59:13 Jan Friedrich wrote:
>
> > Hi,
> >
> > and here is my +1.
> >
> > W
Volcan,
Please stop complaining about the hours I've already sunk into validation
on 3 different operating system on two different machines. You're not
helping the cause.
I can't help but notice the irony that one of the failures is in the
"reproducible" part of the build.
>From my point of view
Why doesn't the maven build in the review kit (below) invoke clean goal?
Gary
On Tue, Sep 3, 2024, 11:37 AM wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> pkarwasz pushed a commit to branch main
> in repository https://gitbox.apache.org/repos/asf/logging-parent
Thank you Piotr!
Gary
On Tue, Sep 3, 2024, 11:17 AM Piotr P. Karwasz
wrote:
> Hi all,
>
> On Sat, 31 Aug 2024 at 21:30, Piotr P. Karwasz
> wrote:
> >
> > This is a vote to release the Apache Log4j `2.24.0`.
> >
> > Website: https://logging.staged.apache.org/log4j/2.24.0/index.html
> > GitHub:
xception
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :log4j-api-test
Gary
On Sun, Sep 1, 2024 at 7:11 PM Gary Gregory wrote:
>
> On Sun, Sep 1, 2024 at 6:01 PM Piotr P. Karwasz
> wrote:
> >
> > Hi Gary,
> &g
On Sun, Sep 1, 2024 at 6:01 PM Piotr P. Karwasz wrote:
>
> Hi Gary,
>
> On Sun, 1 Sept 2024 at 23:34, Gary Gregory wrote:
> > Now I get:
> >
> > [INFO] Results:
> > [INFO]
> > [ERROR] Failures:
> > [ERROR] NetUtilsTest.testCanonicalHostName:7
On Sun, Sep 1, 2024 at 5:09 PM Piotr P. Karwasz wrote:
>
> Hi Gary,
>
> On Sun, 1 Sept 2024 at 23:00, Piotr P. Karwasz
> wrote:
> > On Sun, 1 Sept 2024 at 22:44, Gary Gregory wrote:
> > > [ERROR] sha512 mismatch log4j-bom-2.24.0-cyclonedx.xml: investigate
>
Hi All,
Thank you Piotr for preparing the RC.
Using the review kit, this is what I get on the step 'sh mvnw
-Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO'
[INFO] --- artifact:3.5.1:compare (default-cli) @ log4j-bom ---
[WARNING] property is inherited, it
should be defined in po
I've not looked at details but Ralph's comment hints that we need to
explain to users how to migrate if it's anything more than an import
change. WDYT?
Gary
On Sat, Aug 31, 2024, 5:06 PM Ralph Goers
wrote:
> The API section has
>
> Thread Context is mostly superseded by Scoped Context, which, u
Hi,
I'd like to follow Ralph's lead on Flune related topics.
Gary
On Thu, Aug 29, 2024, 8:12 AM Piotr P. Karwasz
wrote:
> Hi all,
>
> The `log4j-flume-ng` module _de facto_ contains 3 different appenders:
>
> * an Avro appender, that only depends on Avro and Avro IPC. Since it
> only communica
In fact, it's been broken for ages: when you click on a gitbox repo, it
redirects to github! It should instead display its UI as it did in the
past...
Gary
On Wed, Aug 14, 2024, 10:58 AM Gary Gregory wrote:
> Gitbox is just a very thin UI on top of git, no PRs.
>
> Gary
>
&g
t.
> >
> > There might also be parts of the world where GH is not available but
> Apache
> > servers are (more of a geopolitical issue).
> >
> > Gary
> >
> > On Wed, Aug 14, 2024, 3:43 AM Piotr P. Karwasz
> > wrote:
> >
> >> Hi Gary,
Gmail behaves differently based on the platform.
Gary
On Wed, Aug 14, 2024, 7:24 AM Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On Wed, 14 Aug 2024 at 12:34, Gary Gregory wrote:
> > I think that to "deactivate" the mailing lists you refer to would be very
> > bad and
14, 2024, 3:43 AM Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On Fri, 9 Aug 2024 at 12:15, Gary Gregory wrote:
> > While it is a different community, I have received negative feedback in
> > Commons against the trend to spread information all over the place, and
> we
> > don&#x
Isn't that assertable from a unit test?
Gary
On Tue, Aug 13, 2024, 6:00 PM Ralph Goers
wrote:
> Piotr, I am still concerned that you never looked into the issues I had
> with StringArrayThreadContextMap. My performance tests were showing that it
> was fast because it wasn’t actually setting val
John,
You should test our snapshot builds just in case ;-)
Gary
On Tue, Aug 13, 2024, 3:43 PM Piotr P. Karwasz
wrote:
> Hi John,
>
> On Tue, 13 Aug 2024 at 21:10, John Engebretson
> wrote:
> > HI - just curious when the updated ThreadContextMap will be available?
> > The latest release is 2
Hi,
Does the tech we use to build/host allow for the inclusion of a search
box, say at the top? Javadoc now includes a search box which is quite
a nice feature IMO.
Gary
On Fri, Aug 9, 2024 at 3:02 AM Piotr P. Karwasz wrote:
>
> Hi all,
>
> We finished revamping the documentation of Log4j 2. Th
On the front page:
"Batteries included"
Err... what? Let's not get cute here please.
Gary
On Fri, Aug 9, 2024 at 3:02 AM Piotr P. Karwasz wrote:
>
> Hi all,
>
> We finished revamping the documentation of Log4j 2. The result is
> available on the staging site:
>
> https://logging.staged.apache.or
ly together and report and fix issues.
Since I've not heard of problems from people asking for JPMS with our new
jars, i can only assume it works for them.
Gary
On Fri, Aug 9, 2024, 2:00 PM Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On Fri, 9 Aug 2024 at 15:24, Gary Gregory wrote:
rid of
warnings or errors to run an app.
IOW, JPMS is something to work around and not with.
If I had more time, I'd fork a JVM and add a --jpms-off flag...
Gary
On Fri, Aug 9, 2024, 8:59 AM Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On Fri, 9 Aug 2024 at 13:18, Gary Gregory wrote:
&g
... or working _way to hard_.
Gary
On Fri, Aug 9, 2024, 7:10 AM Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On Fri, 9 Aug 2024 at 12:00, Gary Gregory wrote:
> >
> > I hope you mean a new maven module and not a whole new git repo...
>
> Unfortunately I mean repo. The
FYI
While it is a different community, I have received negative feedback in
Commons against the trend to spread information all over the place, and we
don't use GitHub.
The TLDR is that in the past it was easier to find information because you
only had the mailing list and later Jira. Now you hav
I hope you mean a new maven module and not a whole new git repo...
Gary
On Fri, Aug 9, 2024, 2:35 AM Piotr P. Karwasz
wrote:
> Hi all,
>
> Unless I am mistaken, adding tests that run under JPMS is problematic
> in the `apache/logging-log4j2` repository. Even if I create a new
> Maven module for
Hi Piotr,
I just followed the instructions so it's likely these are incorrect or
imprecise.
Gary
On Sun, Aug 4, 2024 at 1:00 PM Piotr P. Karwasz wrote:
>
> Hi Gary,
>
> On Sun, 4 Aug 2024 at 02:09, Gary Gregory wrote:
> >
> > Could the "review kit" ins
Could the "review kit" instructions be incorrect then? I'm pretty sure I
just followed the steps.
Gary
On Sat, Aug 3, 2024, 6:15 PM Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On Sat, 3 Aug 2024 at 23:47, Gary Gregory wrote:
> >
> > Using the review kit, runni
Darwin Kernel Version 23.6.0: Fri Jul 5 17:54:20
PDT 2024; root:xnu-10063.141.1~2/RELEASE_X86_64 x86_64
Gary
On Sat, Aug 3, 2024 at 5:46 PM Gary Gregory wrote:
>
> Using the review kit, running:
>
> sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO
>
> I
Using the review kit, running:
sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO
I get:
[INFO] --- artifact:3.5.0:compare (default-cli) @ log4j-api-kotlin-parent ---
Downloading from reference:
https://repository.apache.org/content/repositories/orgapachelogging-1290/org/apac
Hi. My view is do nothing until we get a new official logo. You don't want
to create any branding confusion IMO.
Gary
On Tue, Jul 23, 2024, 8:00 AM Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On Tue, 23 Jul 2024 at 13:41, Gary Gregory wrote:
> >
> > Don't create an
Don't create and use a new Apache logo without Apache marketing involved
(or whichever part of Aapche is doing this).
Gary
On Tue, Jul 23, 2024, 4:01 AM Piotr P. Karwasz
wrote:
> Hi Ralph,
>
> On Tue, 23 Jul 2024 at 08:25, Ralph Goers
> wrote:
> >
> > What am I missing here? In looking at all
is really opposed to it or if it is just a
> general comment
>
> On Sat, Jul 20, 2024, at 12:01, Gary Gregory wrote:
> > That sounds good.
> >
> > I'm not doing the work here but I would imagine that if I did I'd only
> want
> > to do it once ;-) For
we want to remove OR
> replace existing images. Primarily to avoid breaking links, but ultimately
> also updating marketing material in a retrospective.
>
> On Fri, 19 Jul 2024, 21:41 Gary Gregory, wrote:
>
> > I think this is a bad idea because it is putting the cart before the
&
I think this is a bad idea because it is putting the cart before the horse
as we say in English. Let Apache come up with our new branding and then use
that. It seems all feathers of any kind are not allowed?
Gary
On Fri, Jul 19, 2024, 2:15 PM Christian Grobmeier
wrote:
> Hello,
>
> following th
xt-data I want to make sure that what we are
> leaving will be compatible.
>
> Ralph
>
> > On Jun 20, 2024, at 4:15 AM, Gary Gregory
> wrote:
> >
> > I lost track of where we are after our video discussion regarding all the
> > scoped classes and 2.24.0.
On Thu, Jun 20, 2024 at 8:50 AM Piotr P. Karwasz
wrote:
>
> Hi Gary,
>
> On Thu, 20 Jun 2024 at 13:55, Gary Gregory wrote:
> > I'll give you all my -1 POV here:
>
> I share some of your concerns.
> My main motivation for this experiment with Develocity is not to s
On Thu, Jun 20, 2024 at 7:37 AM Piotr P. Karwasz
wrote:
>
> Hi Gary,
>
>
> On Thu, 20 Jun 2024 at 13:15, Gary Gregory wrote:
> > I lost track of where we are after our video discussion regarding all the
> > scoped classes and 2.24.0. Where are we on those?
>
> F
n Tue, May 28, 2024, 12:27 PM Matt Sicker wrote:
> Probably discussions about the ScopedContext API in general.
>
> > On May 26, 2024, at 14:49, Ralph Goers
> wrote:
> >
> >
> >
> >> On May 26, 2024, at 11:06 AM, Christian Grobmeier
> wrote:
> &
I sure hope that all tests are ALWAYS run by default in the 2.x branch,
otherwise it will be a -1 from me.
Gary
On Fri, Jun 14, 2024, 11:07 AM wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> pkarwasz pushed a commit to branch 2.x
> in repository https://gitbox.a
I'd like to have the PMC meet to review and discuss ScopedContext,
which I am not caught up on, and whatever else we should chat about.
Gary
On Fri, May 24, 2024 at 2:11 PM Piotr P. Karwasz
wrote:
>
> Hi John,
>
> On Fri, 24 May 2024 at 17:17, John Engebretson wrote:
> > The long-debated Scoped
Agreed. The commit history is the best source of authorship anyway.
Gary
On Tue, May 14, 2024, 12:05 PM Ralph Goers
wrote:
> IMO, yes. I had them due to something needed them in the tooling we used
> to use. But like code, tags in the docs aren’t very valuable.
>
> Ralph
>
> > On May 14, 2024,
t is MongoDb.
> > > 1.c. Deprecate module log4j-mongodb4 in favor of log4j-mongodb
> > >
> > > 2. Branch main
> > > 2.a. Rename module log4j-mongodb4 to module log4j-mongodb
> > > 2.b. Rename XML element MongoDb4 to MongoDb
> > >
> > >
I agree with Piotr. I prefer the simplest solution, pointing to
`index.html`, no guessing required.
Gary
On Sat, Apr 20, 2024 at 4:17 PM Piotr P. Karwasz
wrote:
>
> Hi,
>
> I scanned our https://logging.apache.org/ website and found out that
> the internal hyperlinks between our pages are not co
But then your config has to say AND depend on the mongodb5
module! Still confusing 😕
On Wed, Apr 17, 2024, 2:29 PM Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On Wed, 17 Apr 2024 at 18:45, Gary Gregory wrote:
> > Maybe if want to only use the latest driver for main, we shou
Maybe if want to only use the latest driver for main, we should rename the
module and classes and drop the "4". That or go with what I initially
suggested.
Gary
On Wed, Apr 17, 2024, 12:18 PM Gary Gregory wrote:
> Hi Piotr,
>
> Having mongodb4 module depend on the mongo
Hi Piotr,
Having mongodb4 module depend on the mongodb 5 driver sure is confusing
though. What I don't know and don't want to deal with is "I updated to the
latest log4j-mongdb5 version and my app no longer works" because it might
turn out that the newer 5.x driver drops support for older Mongo ve
What's the difference with RC2?
TY,
Gary
On Thu, Mar 21, 2024, 11:46 AM Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Tools 0.8.0 (RC3).
>
> Website: https://logging.staged.apache.org/log4j/tools
> GitHub: https://github.com/apache/logging-log4j-tools
> Commit: 7d157b61e198e
+1
Tested src zip file
SHA512 OK
ASC OK
Apache RAT check OK
Build 'mvn clean verify' OK
Using:
openjdk version "17.0.10" 2024-01-16
OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
Apache Maven 3.9.6 (bc0240f3c744dd6
Ah, ok, then I'll abstain from voting until we have a version I can
build locally.
TY for the heads up.
Gary
On Fri, Mar 15, 2024 at 2:24 PM Jan Friedrich wrote:
>
> Hello Gary,
>
> https://paste.apache.org/1ropz looks like you're building 2.0.16?
> Building the current version is currently ver
What about the failure?
Gary
On Fri, Mar 15, 2024, 11:35 AM Davyd McColl wrote:
> Hi
>
> Yes, everything should be done via npm scripts. So I should remove any
> confusing .cmd files.
>
> As for the version, I should update that, but it's minor. That version
> comes from package.json and will o
any holdups and that was due to outdated build
> docs from me - so it should be resolved. There were no -1's, and at
> least 4 +1's that I saw. I'll try to keep better tally next time.
>
>
> -d
>
> On 2024/03/08 14:22, Gary Gregory wrote:
> > Process:
>
Process:
You need to reply to this thread with a [RESULT] prefix, tally all the
votes, and say whether the vote passes or not. It is helpful to note which
votes are binding or not.
Gary
On Fri, Mar 8, 2024, 6:06 AM Davyd McColl wrote:
> Hi all
>
>
> Thanks for all the checking - log4net 2.0.16
All better now: +1
For details see: [log4j] `2.23.1` reproducibility failure (Was: [VOTE]
Release Apache Log4j 2.23.1)
Gary
On Wed, Mar 6, 2024 at 9:26 AM Gary Gregory wrote:
>
> Same :-(
>
> [INFO] --- bnd-baseline:7.0.0:baseline (check-api-compat) @ log4j-bom ---
> [INF
The build was completed successfully.
Gary
On Wed, Mar 6, 2024 at 11:02 AM Gary Gregory wrote:
>
> I nuked the whole thing (rm -rf ~/.m2/repository/) for good measure
> (I'll do that once a month from now on).
>
> Building (and downloading the world)...
>
> It'
Could you do `rm -rf ~/.m2/repository/org/apache/commons` and retry,
> please? (If you compare `target/bom.xml`s you can see that your local
> `commons-*` clones have different hashes.)
>
> On Wed, Mar 6, 2024 at 4:00 PM Gary Gregory wrote:
>
> > On Wed, Mar 6, 2024 at 9:54 AM Vo
On Wed, Mar 6, 2024 at 9:54 AM Volkan Yazıcı wrote:
>
> Could you share the `target/bom.xml` and
https://paste.apache.org/za0k3
> `target/log4j-bom-2.23.1.buildinfo` files too, please?
https://paste.apache.org/1403q
Gary
>
> On Wed, Mar 6, 2024 at 3:35 PM Gary Gregory wrot
Which command are you exactly running?
>
> Could you share the `target/bom.xml` and `target/log4j-bom-2.23.1.buildinfo`
> files too, please?
>
> On Wed, Mar 6, 2024 at 3:28 PM Gary Gregory wrote:
>>
>> Same :-(
>>
>> [INFO] --- bnd-baseline:7.0.0:baseline (che
Gary
On Wed, Mar 6, 2024 at 9:23 AM Volkan Yazıcı wrote:
>
> Could you retry after cleaning up your local repository, please? That is,
>
> rm -rf ~/.m2/repository/org/apache/logging/log4j/*/2.23.1*
>
>
>
> On Wed, Mar 6, 2024 at 3:03 PM Gary Gregory wrote:
>
I get a build failure:
INFO] --- artifact:3.5.0:compare (default-cli) @ log4j-bom ---
[ERROR] project.build.outputTimestamp property should not be inherited
but defined in POM /Users/garydgregory/rc/log4j/src/.flattened-pom.xml
Downloading from reference:
https://repository.apache.org/content/repo
Hi,
Thank you for creating this RC.
It would be more helpful to provide cut-and-paste instructions. This
does not work obviously:
svn co https://dist.apache.org/repos/... && cd $_
Neither the "svn co" nor the cd "$_" will work ;-)
Gary
On Wed, Mar 6, 2024 at 8:13 AM Volkan Yazıcı wrote:
>
>
+1
Note that the verification instructions below or the distro process or
both need changes because the wget and all commands get EVERYTHING and
work on EVERYTHING, which in this case means that BOTH release
candidates for 2.23.0 and 3.0.0-beta2 are downloaded and instructions
work on both at the
+1
- Testing src zip file.
- ASC OK
- SHA512 OK
- mvn clean verify OK
openjdk version "17.0.9" 2023-10-17
OpenJDK Runtime Environment Homebrew (build 17.0.9+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.9+0, mixed mode, sharing)
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Ma
Cool beans.
Gary
On Sat, Feb 17, 2024, 12:55 AM Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On Sat, 17 Feb 2024 at 03:12, Gary Gregory wrote:
> >
> > Hi Piotr,
> >
> > Are you planning for a RC?
>
> Yes, I'll prepare a release this weekend.
>
> Piotr
>
Hi Piotr,
Are you planning for a RC?
Gary
On Wed, Feb 14, 2024 at 8:12 AM Gary Gregory wrote:
>
> FYI, the 1.2 bridge is fixed now. Not sure if the bug is present or not for
> JUL.
>
> Gary
>
> On Mon, Feb 12, 2024, 8:07 AM Piotr P. Karwasz
> wrote:
>>
>>
Keep in mind that decisions for the project still must be recorded on the
mailing list. This might be a silly reminder since the issue is the same
with Jira. Let's just be mindful of this information tracking as we've
moved more of our infrastructure to GitHub. Don't get me wrong, I love
working wi
FYI, the 1.2 bridge is fixed now. Not sure if the bug is present or not for
JUL.
Gary
On Mon, Feb 12, 2024, 8:07 AM Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On Mon, 12 Feb 2024 at 13:22, Gary Gregory wrote:
> >
> > I'll continue later today to try and fix the set L
I think I invented this extra stuff back when I was co-writing a
proprietary, complex, and feature-rich JDBC driver. I no longer live
in that particular code base, but I can say that writing this kind of
code and implementing a specification like JDBC makes you write code
to a logging library rathe
+1
Gary
On Mon, Feb 12, 2024 at 4:32 PM Christian Grobmeier
wrote:
>
> Hello,
>
> This vote is to put Chainsaw to the "Dormant" components. There is much work
> to be done on this component, but not enough hours can be committed to do
> that work. To reflect this situation to the user, it is b
I'll continue later today to try and fix the set Level issue...
Gary
On Mon, Feb 12, 2024, 6:15 AM Piotr P. Karwasz
wrote:
> Hi all,
>
> This week I was planning to perform a 2.23.0 release. According to
> Github most of the issues scheduled for this milestone are resolved:
>
> https://github.c
To make sure I understand, you are saying the bug is in
org.apache.logging.log4j.core.Logger.setLevel(Level)?
Gary
On Sat, Feb 10, 2024 at 5:24 PM Piotr P. Karwasz
wrote:
>
> Hi Gary,
>
> On Sat, 10 Feb 2024 at 18:14, Gary Gregory wrote:
> > In my branch
> > https:/
Thank you Piotr! I'll poke around...
Gary
On Sat, Feb 10, 2024, 5:24 PM Piotr P. Karwasz
wrote:
> Hi Gary,
>
> On Sat, 10 Feb 2024 at 18:14, Gary Gregory wrote:
> > In my branch
> https://github.com/garydgregory/commons-logging/tree/log4j1-log42-api
> > I have tes
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
gt; >> On Thu, Jan 25, 2024, 11:33 PM Ralph Goers
> >> wrote:
> >>
> >> OK. The only good way to handle that is to parse the YAML/JSON file
> while
> >> streaming it and extract just the fields you want to include in the
> logs.
> >>
>
just the fields you want to include in the logs.
>
> Ralph
>
> > On Jan 25, 2024, at 6:40 PM, Gary Gregory
> wrote:
> >
> > Well, it's worse than that because the object is an object created by
> > parsing a YAML (or JSON) file, then the toString()
Well, it's worse than that because the object is an object created by
parsing a YAML (or JSON) file, then the toString() of that object
renders a String in some other format.
Gary
On Thu, Jan 25, 2024 at 7:45 PM Ralph Goers wrote:
>
> Volkan & Matt,
>
> Neither of those is going to help. The iss
Obvious mistake:
logger.debug("This is fun", myFunObject::toString)
->
logger.debug("This is fun {}", myFunObject::toString)
Gary
On Thu, Jan 25, 2024, 11:55 AM Gary D. Gregory wrote:
> Hi All,
>
> I'd like to ask how to if we can devise advice around an issue I ran into
> this week.
>
> One
Using the same API jar for 3.x core is intriguing. I like the idea of
a cleaned-up API jar (no custom Supplier) that can front 2.x and 3.x.
I'd love to hash this out in a call.
Gary
On Thu, Jan 18, 2024 at 12:02 AM Ralph Goers wrote:
>
> The quick answer to this question is “I don’t know”. When
; proposition” of Log4j? Why should people choose Log4j over the
> alternatives?
>
> This is a positioning question; what are the strengths and weaknesses of
> Log4j and how should Log4j position itself in the market of logging
> solutions?
>
> Remko
>
>
> > On Jan 15
Should these files contain comments to this effect?
Gary
On Tue, Jan 16, 2024, 1:18 AM Piotr P. Karwasz
wrote:
> Hi Ralph,
>
> On Tue, 16 Jan 2024 at 01:56, Ralph Goers
> wrote:
> >
> > I don’t understand what it means to keep both staging and publish in
> “asf-site”. By definition, the asf-si
We should IMO keep this information available _somewhere_, maybe in a new
stable historical-archival section of the site. I'm not a fan of using the
wiki because that's yet another place to look for information and it feels
transitory, unstable (as far as information permanance), and more like
some
It feels wrong to add support for a special development time tool in our
runtime.
Gary
On Thu, Jan 11, 2024, 1:58 PM Ralph Goers
wrote:
> Yeah - if we add it to the code base that implies that we are testing it.
> I really don’t want to be in the position where we start adding
> customizations
Nice! 😀
On Tue, Jan 9, 2024, 4:45 PM Ralph Goers wrote:
> FYI - in
> https://github.com/spring-projects/spring-boot/issues/33450#issuecomment-1883014368
> has confirmed that Log4j 3.0.0-beta1 now works correctly with Spring 3.x.
>
> Ralph
FWIW, I'm NOT a fan of the static analysis option. Good design should be
reflected in the code. We should not pick suboptimal abstractions (or no
abstraction in this case) plus static analysis to validate odd design
choices.
Gafy
On Thu, Jan 4, 2024, 11:29 AM Piotr P. Karwasz
wrote:
> Hi Ralph,
P. Karwasz
wrote:
>
> Hi Gary,
>
> On Sat, 23 Dec 2023 at 17:45, Gary Gregory wrote:
> >
> > +1
> > - Tested src zip file
> > - ASC OK
> > - SHA512 OK
> > - `mvn clean verify` OK
> > - Using:
> > Apache Maven 3.9.6 (bc0240f3c744dd6b6
+1
- Tested src zip file
- ASC OK
- SHA512 OK
- Building 'mvn clean verify' OK
- Using:
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /usr/local/Cellar/maven/3.9.6/libexec
Java version: 17.0.9, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.9/libexec/openjd
3 Dec 2023 at 17:47, Gary Gregory wrote:
> >
> > Question: Where is the git tag in these VOTE emails? I see a "Commit"
> > but no named tag.
>
> The CI does not create tags, but it works on a separate branch
> `release/x.y.z` and the commit should be the last commi
TY for the references.
Gary
On Sat, Dec 23, 2023 at 2:20 PM Piotr P. Karwasz
wrote:
>
> Hi Gary,
>
> On Sat, 23 Dec 2023 at 16:23, Gary Gregory wrote:
> >
> > Can this noise be made quiet in the future please (mvn clean verify -U):
>
> This is a temporary workaro
Question: Where is the git tag in these VOTE emails? I see a "Commit"
but no named tag.
Gary
On Fri, Dec 22, 2023 at 1:01 PM Piotr P. Karwasz
wrote:
>
> This is a vote to release the Apache Log4j 2.22.1.
>
> Website: https://logging.staged.apache.org/log4j/2.x/
> GitHub: https://github.com/apach
+1
- Tested src zip file
- ASC OK
- SHA512 OK
- `mvn clean verify` OK
- Using:
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /usr/local/Cellar/maven/3.9.6/libexec
Java version: 17.0.9, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.9/libexec/openjdk.jdk/Con
Can this noise be made quiet in the future please (mvn clean verify -U):
...
[INFO] --- bsh:1.4:run (process-sbom) @ log4j-api-java9 ---
[INFO] Executing Script
[INFO] file class java.lang.Object
[INFO] script class java.lang.String
[INFO] evaluating script import java.io.*;
import java.nio.file.*
1 - 100 of 1416 matches
Mail list logo
