Re: [log4j] Performance comparsion

Goers <ralph.go...@dslextreme.com> > > wrote: > > > > > > I posted a comment on the post as I think he missed a couple of things. > > > > > > Ralph > > > > > >> On Apr 13, 2017, at 11:38 AM, Christian Grobmeier <grobme...@apach

Re: [log4j] Performance comparsion

On Thu, Apr 13, 2017, at 22:47, Ralph Goers wrote: > You have commit rights…. ;-) hehe :-) And I actually feel the Open Source itch! Hopefully I can make some proposal! > Ralph > > > On Apr 13, 2017, at 11:41 AM, Christian Grobmeier <grobme...@apache.org> > > wrote:

Re: [log4php]

Hi, On Thu, May 17, 2018, at 00:20, Rocska Ádám wrote: > I have just recently joined, and I plan to do my first contributions on > log4php. Welcome! > For my next iteration I would like to focus on the following : > I'd like to have a full namespace coverage throughout the repo. +1 We have a

Re: [LOG4PHP] Site Generation

I would love if we could separate the logging pages from the release cycle. There was once a blocker using Phing, I think it had something to do with not supporting UTF-8 correclty. Most likely this is gone by now and I would be fine to move on. -- Christian Grobmeier grobme...@gmail.com

Re: log4php update

I remember correctly) Christian > > Kate > > From: Kate Gray > Sent: Tuesday, October 29, 2019 4:30 PM > To: Christian Grobmeier > Subject: Re: log4php update > > Is this it? > > https://cwiki.apache.org/confluence/display/LOGGINGLOG4PHP/ReleaseProcedure &g

Re: [LOG4PHP] Abandoned? Contributing?

Hello Kate, On Sun, Oct 27, 2019, at 06:46, Kate Gray wrote: > As I said, I'd be glad to. I started working on getting log4php > working properly for PHP 7, as PHP5 is end of life, and no longer > updated. I am one of the original developers of Log4php (at Apache). Unfortunately, I had not

Re: log4php update

I think we once had a release guide, but I also think it was on a wiki which was removed? https://cwiki.apache.org/confluence/display/logging-log4php Guess we have to renew it -- Christian Grobmeier grobme...@gmail.com On Thu, Sep 12, 2019, at 17:48, Matt Sicker wrote: > Do we h

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

Hello, I am not an expert on c++ or something, but I looked on the content, read this thread and think it is safe to release this. However, my hope is that in future more competent cxx devs than me would check it :) I vote +1 also Cheers, Christian On Mon, Aug 17, 2020, at 08:08, Ralph Goers

Re: [VOTE] Move Log4PHP to dormant status

Very sad, but +1. Code base became very old and there is lots to do. -- The Apache Software Foundation V.P., Data Privacy On Wed, Dec 9, 2020, at 22:20, Ralph Goers wrote: > I started a discussion several days ago regarding moving Log4PHP to > dormant status and have gotten no feedback. Given

Re: [DISCUSS] Starting social media accounts for subprojects

I think thats long overdue and recall we had a component Twitter account for log4php. Later today I will check if I can find the passwords. The component is dormant, but its worth having access shared with the PMC still https://twitter.com/log4php/ -- The Apache Software Foundation V.P., Data

Re: [VOTE] Future of Log4j 1.x

On Sat, Jan 1, 2022, at 18:19, Jochen Wiedmann wrote: > On Sat, Jan 1, 2022 at 4:40 PM Xeno Amess wrote: > >> > People should migrate to log4j2. >> good thinking, but what if they migrate to logback... > > No, it's not (good thinking, that is). > > Log4j1 is a part of basically *every* Java

Re: [RESULT][VOTE] Move apache/log4j1 Git repo to apache/logging-log4j1 Git repo

o the updated summary is > > Binding +1 votes were received from Ralph Goers, Dominik Psenner, Matt > Sicker, Ron Grabowski, and Remko Popma > Binding -1 votes were received from Gary Gregory and Christian Grobmeier > A non-binding +1 vote was received from Carter Kozak, Robert Middleton, >

Re: [DISCUSS] The future of Log4j 1.x

ed end of life in August 2015. Log4j 1.2.17 >> > was released on May 26, 2012. The last commit was to update the >> > web site 7 years ago. The changes.xml file shows there were commits up to >> > sometime in 2012, all of which were performed by Gary Gregory >> >

Re: Resurrecting log4j 1.x

Hi On Fri, Dec 24, 2021, at 06:29, Vladimir Sitnikov wrote: > Christian>Here is some more information on how we develop software: > > Christian, I'm a member of PMC in Apache JMeter and Apache Calcite, ok? I was not aware of that, but the way you discussed looked like it was helpful to send

Re: [VOTE] Move apache/log4j1 Git repo to apache/logging-log4j1 Git repo

Hi Vladimir, On Fri, Dec 24, 2021, at 13:51, Vladimir Sitnikov wrote: > Dominik, > > Are you willing to add committers and PMC members to the log4j 1.x > community? if we add people, then we add it to the logging project. There is no separate log4j/log4php whatever community. We are one

Re: [DISCUSS] The future of Log4j 1.x

Thank you very much Ralph for compiling this list. On Fri, Dec 24, 2021, at 17:47, Ralph Goers wrote: > 1. Create a README.md that publishes the projects EOL status and do > nothing else. > 2. Create a README.md that says the project is EOL and no further big > fixes or enhancements will be

Re: Resurrecting log4j 1.x

Hello Vladimir, On Thu, Dec 23, 2021, at 20:58, Vladimir Sitnikov wrote: > Christian>if you send in patches there are people who would apply them > > Thank you. > Let us see what INFRA says regarding https://github.com/apache/log4j in > https://issues.apache.org/jira/browse/INFRA-22654 This is

Re: [VOTE] Move apache/log4j1 Git repo to apache/logging-log4j1 Git repo

hi at the moment I am -1 too, mostly for the reasons Gary mentioned. Most important is that we don't have a clear goal on what we are trying to achieve here. We should be very explicit of why we are doing what. Cheers, Christian On Thu, Dec 23, 2021, at 22:50, Gary Gregory wrote: > -1 > We

Re: Log4J 1.x progress, pull request(s), plans

On Thu, Dec 23, 2021, at 16:39, Leo Simons wrote: > On Thu, 23 Dec 2021 at 15:43, Christian Grobmeier > wrote: > >> I didn't see the PRs though - are they still local on your box? > > > On the wrong repo and lacking a target branch: > > https://github.co

[RESULT][VOTE] Future of Log4j 1.x

(binding) Christian Grobmeier (binding) Carter Kozak (binding) Ron Grabowski (binding) Volkan Yazıcı (binding) Remko Popma (binding) Davyd McColl (binding) +0: Xeno Amess (non binding) -1: Vladimir Sitnikov (non binding) The PMC decided unanimous to keep Log4 1 EOL. Since there was a lengthy

Re: Log4J 1.x progress, pull request(s), plans

. I think so. I didn't see the PRs though - are they still local on your box? Kind regards, Christian > > Cheers, > > Leo > > > On Thu, 23 Dec 2021 at 14:34, Gary Gregory wrote: > >> On Thu, Dec 23, 2021 at 8:20 AM Christian Grobmeier >> wrote: >

Re: New Log4j 1 repo

Hi, On Thu, Dec 23, 2021, at 13:33, Vladimir Sitnikov wrote: >>using maven toolchain feature > > Are toolchains really needed, especially, 1.6 and 1.7? > I believe Java "target=1.4" + Java 1.8 would be good enough. > If there are javadoc "warnings or errors", we could just suppress it. > At the

Re: Log4J 1.x progress, pull request(s), plans

ave in > 2.x. That said, if we decides to move forward with 1.2.18, I'll help. > > No matter what, it needs to be a decision made carefully and not in haste. > +1 > Gary > > On Thu, Dec 23, 2021 at 7:56 AM Christian Grobmeier > wrote: > >> Hello >> >

Re: Log4J 1.x progress, pull request(s), plans

Hello I have been the person cutting the 1.2.17 release and what I remember was it was a super hard build. I had to install some VMs because there were weird dependencies to this build. Building it fully will not be easy, but I can also look into some mails whatever I found from that time.

Re: [DISCUSS][VOTE] Future of Log4j 1.x

Makes sense. I will close thus vote not earlier than Jan 5, if there is no further objections. Thanks for your input Tim -- The Apache Software Foundation V.P., Data Privacy On Thu, Dec 30, 2021, at 01:56, Tim Perry wrote: > I propose that this vote should stay open longer than 72 hours given

Re: [DISCUSS][VOTE] Future of Log4j 1.x

If there is long term commitment apart from these urgent fixes we can run another vote. You cannot guarantee you are alive by February, nobody can give such guarantees. The logging pmc is not here to accept all patches as they come in but to make decisions best to the project (among other

Re: [DISCUSS] The future of Log4j 1.x

-ck >> >> On Fri, Dec 24, 2021, at 11:47, Ralph Goers wrote: >> > As we all know Log4j 1.x reached end of life in August 2015. Log4j >> 1.2.17 was released on May 26, 2012. The last commit was to update the >> > web site 7 years ago. The changes.xml file sho

Re: [VOTE] CVE creation process

+1, as this only affects the creation of cves but does not block the fixing going on immediately. I think we do not require majority though, just waiting if someone objects is fine for me On Mon, Jan 3, 2022, at 12:59, Volkan Yazıcı wrote: > Hello, > > As discussed earlier[1], this is a vote to

Re: [VOTE] Future of Log4j 1.x

+1, Option 1 On Wed, Dec 29, 2021, at 20:33, Christian Grobmeier wrote: > Hello, > > as discussed in another thread, this is a vote about the future of > log4j 1. This vote stays open for the usual 72h. > Options are explained below. > > You can vote for: > >

Re: [DISCUSS][VOTE] Future of Log4j 1.x

Hi Leo, good new year to you! On Sun, Jan 2, 2022, at 07:12, Leo Simons wrote: > Hey, > > Happy new year everyone! > > On Wed, Dec 29, 2021 at 8:54 PM Ralph Goers > wrote: > >> Leo seemed interested at first but didn’t weigh in on the discussion >> thread. > > > I'm here. I did mention in a

Re: Resurrecting log4j 1.x

Hello On Thu, Dec 23, 2021, at 18:07, Vladimir Sitnikov wrote: > Dominik> There are fixes for the flaws of log4j1 available: migrate to > log4j2 > > How does migration help me if I want to get 1.x fixed? > log4j2 is a different product, created by a different team. > Why should I migrate to

[VOTE] Future of Log4j 1.x

Hello, as discussed in another thread, this is a vote about the future of log4j 1. This vote stays open for the usual 72h. Options are explained below. You can vote for: [ ] +1, Option 1 [ ] +1, Option 2 [ ] +/- 0, abstain [ ] -1 object against those options Option 1: Create a README.md

Re: [logging-log4j1] branch v1.2.8 created (now 0cde9dd)

Hello, On Fri, Jan 7, 2022, at 08:21, Ceki Gülcü wrote: > As for infringing on the log4j trademark, I will rename the repo to > something else, for example "re4j". > > As mentioned in my previous message, if the ASF decides to integrate > "re4j" as log4j 1.x, the door is open. Thanks. You did

Re: [ANNOUNCE] Log4j 1 End-of-Life Statement

Hello Ceki On Thu, Jan 6, 2022, at 11:00, Ceki Gülcü wrote: > The fact that the decision was unanimous on such a delicate matter is > quite surprising and very interesting in itself with respect to group > dynamics. You haven't been at the meeting. That's why you don't know anything about this

Re: [ANNOUNCE] Log4j 1 End-of-Life Statement

Hi On Thu, Jan 6, 2022, at 15:05, Ceki Gülcü wrote: > On 06/01/2022 14:42, Christian Grobmeier wrote: >> Which ones? The JMSAppender issue or the SockerServer issue? Both have been >> there >2012. What is suddenly so critical it requires re-releasing EOL >> s

Re: [logging-log4j1] branch v1.2.8 created (now 0cde9dd)

elease, especially >> > if there is continued community interest in it. Otherwise, I still >> > believe it's more useful to patch up the existing v2/v1 compatibility >> > system so that users can drop in v2 to upgrade things much more >> > easily, especially given the

Re: [VOTE] Release Apache Logging Parent 1.10.0

Lgtm as far as I can tell :) +1 On Tue, Sep 5, 2023, at 11:15, Piotr P. Karwasz wrote: > Hi Volkan, > > On Tue, 5 Sept 2023 at 11:04, Volkan Yazıcı wrote: >> >> Summary: *THE VOTE IS STILL ON* though the Nexus URL should point to >>

Re: [VOTE] Release Apache Logging Parent 10.0.0 (RC4)

+1 On Fri, Sep 8, 2023, at 16:07, Volkan Yazıcı wrote: > This is a vote to release the Apache Logging Parent 10.0.0 (RC4). > > Source repository: https://github.com/apache/logging-parent > Commit: 2af643f84ada9a05e08229d077c6fafee2fed732 > Distribution:

Re: Remove Noise: using commits@?

things split into notifications@ and commits@. Is the issue with >> notifications@? >> >>> On Aug 23, 2023, at 3:19 PM, Robert Middleton wrote: >>> >>> They already go to the notifications list, is that not sufficient? I’m >>> pretty sure that’s how all of the

Re: [Log4j] GitHub Discussions

+1 On Thu, Aug 24, 2023, at 09:26, Volkan Yazıcı wrote: > Piotr shared a very good observation (in a private Slack post > ) that > users ask questions in GitHub Issues, we point them to the mailing list, > and they disappear. See

Staging website (was: [VOTE] Release Apache Log4j 2.21.0)

>> [1] Christian's recent Jekyll experiment on the `asf-staging` branch >> of `logging-site` repository confused the INFRA and it is acting >> strangely. This will *NOT* be an issue when we push the website >> changes to production, i.e., `asf-site` branch. Though we will try >> fixing

[VOTE] Release Apache Log4j 2.21.0

This is a vote to release the Apache Log4j 2.21.0. Website: https://logging-log4j.staged.apache.org/log4j/2.x/ GitHub: https://github.com/apache/logging-log4j2 Commit: 493d9a9daabc72d10582c4682538baa93a2a Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j Nexus:

[ANNOUNCE] Apache Log4j 2.21.0 released

Apache Log4j team is pleased to announce the 2.21.0 release. Apache Log4j is a versatile, industrial-strength Java logging framework composed of an API, its implementation, and components to assist the deployment for various use cases. For further information (support, download, etc.) see the

Re: [VOTE] Release Apache Log4j 2.21.0

Here is my own +1 With that, this vote passes with 5x +1 from: Volkan Yazici Piotr Karawasz Gary Gregory Ralph Goers Christian Grobmeier I will proceed with the following steps soon Thanks to everybody who voted! Christian On Fri, Oct 13, 2023, at 11:08, Christian Grobmeier wrote

Re: Staging sites and repo convention

Hi On Thu, Oct 19, 2023, at 16:31, Ralph Goers wrote: > I am -1 (i.e. - code commit veto) on any code change that causes the > Log4j 2 web site url (https://logging.apache.org/log4j/2.x/) to no > longer work. > Since the staging site is a prelude to the live site I have to assume > this change

Re: Staging sites and repo convention

>> Why are you pissed? I am sorry if I would be the reason > > 1. I indicated I didn’t want changing to Jekyl to be the reason for > changing to Jekyll. So far, that appears to be the reason. I thought > you mentioned something about getting CI to work but the current > process could have

Re: Staging sites and repo convention

On Thu, Oct 19, 2023, at 19:38, Matt Sicker wrote: > If this is only for staging URLs and doesn’t break the production URLs, > this sounds reasonable. +1 Actually, I would love to have staging sorted out first. Once it works as we are used to, I am open to anything. > > And the git worktree

Why is JNDI still necessary?

Hi, on the recent deprecation vote I saw this vote (from Ralph): > * JNDI-related features: -1 Unfortunately, JEE users require this. I am surprised we still have JNDI in the code at all, but this made me curious: why do JEE users need JNDI features for logging? Why can't they just use the

Re: [VOTE] Deprecation of 2.x modules/features and removal in 3.x

+1 to all - deprecation to me means we add a label that we plan to remove it in 3.x, but we are not removing it not. We can step back. Many of those modules don't look as if they need to belong in the main repo. I can accept kubernetes/docker stuff, but not in the main repo. I have a strong +1

Re: [Discuss][VOTE] Deprecation of 2.x modules/features and removal in 3.x

to their own repo. I am aware Gary is opposed to this, but I am strongly in favor to such a move. Reading my message, I see where this confusion comes from; sorry for that. I should have made my two points more clear. Anyway, still voting +1 on deprecation for now > > Ralph > >>

Re: Why is JNDI still necessary?

unctional need. >> >> On Tue, Oct 31, 2023 at 10:55 PM Piotr P. Karwasz >> wrote: >> >>> Hi Christian, >>> >>> On Tue, 31 Oct 2023 at 21:57, Christian Grobmeier >>> wrote: >>>> I am surprised we still have JNDI in the code at

Re: Why is JNDI still necessary?

Hi On Tue, Oct 31, 2023, at 23:23, Matt Sicker wrote: > I’m not sure how much people use this deployment model anymore, but > JNDI was and still is at the core of JavaEE (now JakartaEE) dependency > injection APIs. While CDI is the current way of using dependency > injection there, CDI is

Staging is back

Infra helped me to fix the staging website: https://logging.staged.apache.org/ This website is currently done with jekyll. I will restore the sub website in the next days Since the underlying bug is fixed, I don’t expect any more issues. Please check it out and let me know if you have

Re: Why is JNDI still necessary?

ill simply get a -1 when the PR/commit is attempted from whomever >> gave the -1 vote. In other words, this is NOT a procedural vote but a code >> modification vote that is taking place before the code is modified. >> >> Ralph >> >>> On Nov 1, 2023, at 3:13 AM, Christian Grob

Re: Why is JNDI still necessary?

d after all the countless reviews), but people still don’t. With all that said splitting the repos for2.x still feels right. Christian > Ralph > >> On Nov 1, 2023, at 12:22 PM, Christian Grobmeier >> wrote: >> >> As some might know, I am writing a book and the publisher

Re: Why is JNDI still necessary?

On Thu, Nov 2, 2023, at 08:53, Ralph Goers wrote: >> On Nov 1, 2023, at 9:24 PM, Christian Grobmeier wrote: >> >> >> >> On Thu, Nov 2, 2023, at 02:12, Ralph Goers wrote: >>> Christian, I was at least 3 years ahead of you on this one.This is >>

Re: Features for 3.x was: Why is JNDI still necessary?

On Thu, Nov 2, 2023, at 17:04, Gary Gregory wrote: > Log4j 3 matching Spring 3 seems obviously a good thing to me. Going to Java > 17 seems to me as well a good thing. > > Gary > > On Thu, Nov 2, 2023, 7:04 AM Ralph Goers wrote: > >> I should add that I am concerned that we are missing a huge

Re: Features for 3.x was: Why is JNDI still necessary?

On Fri, Nov 3, 2023, at 03:36, Ralph Goers wrote: >> On Nov 2, 2023, at 10:30 AM, Christian Grobmeier >> wrote: >> On Thu, Nov 2, 2023, at 17:04, Gary Gregory wrote: >>> Log4j 3 matching Spring 3 seems obviously a good thing to me. Going to Java >>>

Re: Features for 3.x was: Why is JNDI still necessary?

On Fri, Nov 3, 2023, at 22:28, Ralph Goers wrote: >> On Nov 3, 2023, at 12:47 PM, Christian Grobmeier >> wrote: >> Sorry, I am a bit lost here - you spoke about Spring 3, and it sounded like >> it was something new. I understand this is nothing new. So, what e

Re: [chainsaw] DB package?

On Tue, Oct 24, 2023, at 22:19, Matt Sicker wrote: > If you use Log4j in Chainsaw, you could set up a JDBC appender or > similar to forward things along. The Flume appender could be useful > there, too, but that sort of moves the database configuration into your > Flume config. I see - but

[chainsaw] DB package?

Hi, in this package: org.apache.log4j.db all classes are commented. I am tempted to just remove it in full, but I am not sure what i was supposed to do. Docs read: "Provides means to append logging events into various databases." Does that mean, Chainsaw would collect logs and then send it

Re: [chainsaw] DB package?

On Tue, Oct 24, 2023, at 22:30, Robert Middleton wrote: > Those classes are to receive log events from a database table. Log4j1 > and log4cxx can write log messages directly to a database; I'm not > sure about log4j2. Yes, there is a JDBC Appender that is discussed more often these days >

Migrating the landing page

Hello, the current landing page: https://logging.apache.org/ is done with JBake. We have rather complicated instructions on how to re-generate the landing page: https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Sites The Infra team recommends Pelican or

Re: Migrating the landing page

pport for Jekyll and Hugo, but I don't like it. There is none for JBake to my knowledge. I an not changing the tooling because I like Jekyll better, but because it is a standard, I have autodeploy tools ready and it generally is better understood than JBake. Kind regards, Christian >

[chainsaw] Developing for Chainsaw

Hi, I tried to start Chainsaw from the official build, using Maven (mvn package) and even starting it using the LogUI main class. All methods failed for various reasons. What is the best method to get Chainsaw started, when trying to fix an issue? Kind regards, Christian When running using

Re: `chainsaw` vs `logging-chainsaw`

On Thu, Sep 21, 2023, at 21:53, Robert Middleton wrote: > I think #1 is a mirror of SVN( > https://svn.apache.org/repos/asf/logging/chainsaw/trunk/), while #2 is a > mirror of the gitbox repository. Looks like the SVN mirror is outdated. Can we safely remove it? If there are no objections, I

Re: `chainsaw` vs `logging-chainsaw`

; TY, > Gary > > On Fri, Sep 22, 2023, 1:50 PM Christian Grobmeier wrote: > >> >> On Thu, Sep 21, 2023, at 21:53, Robert Middleton wrote: >> > I think #1 is a mirror of SVN( >> > https://svn.apache.org/repos/asf/logging/chainsaw/trunk/), while #2 is a >>

Re: Migrating the landing page

shell script for this) to check and let actions do the rest. You can see it in action on the privacy website. > > Ralph > >> On Sep 22, 2023, at 2:03 PM, Christian Grobmeier >> wrote: >> >>  >> >>> On Fri, Sep 22, 2023, at 22:08, Ralph Goers w

Re: [Discuss][VOTE] Move Chainsaw to dormant status

On Thu, Sep 21, 2023, at 19:38, Ralph Goers wrote: > At this point in time I will abstain from voting. As far as I am > concerned only 1 vote counts - Scott’s. He has steadfastly asked that > the project not be retired and until he positively says he will no > longer maintain it I am not

Re: Migrating the landing page

imply provide a set of >>>> global pages (about, support, etc.) in their `main` branch and >>>> version-specific programmer-friendly-formatted (in AsciiDoc!) manuals >>>> stored in branches next to the code they document, e.g., `2.x`, `3.x`, etc. >>>>

Re: Migrating the landing page

pushing this to a website, generating release notes, >> adding a search bar, styling the page, syntax highlighting source code, >> etc. – should be done by a separate "tool" located elsewhere. This will >> enable the committers to stop worrying about the website and it

[chainsaw] Trouble starting it at all

Hi, I have found out Chainsaw requires Java 11. I used this from IntelliJ and run LogUI. However, even when there is no error message, the Splash Screen never disappears. Is there any specific verion of Java I need? These are he last lines i see: 15:15:29.580 [AWT-EventQueue-0] DEBUG

Re: Refining product feature set strategy

I see your point and agree with many things. I suggest we are not (only) making "data-driven" decisions. Most of us do this for fun, not for money. It is perfectly OK to decide just because we like it and enjoy ourselves. You are raising an excellent point: maintenance. We have a lot of stuff

Re: [Discuss][VOTE] Move Chainsaw to dormant status

On Fri, Sep 22, 2023, at 12:51, Christian Grobmeier wrote: > On Thu, Sep 21, 2023, at 19:38, Ralph Goers wrote: >> At this point in time I will abstain from voting. As far as I am >> concerned only 1 vote counts - Scott’s. He has steadfastly asked that >> the project not

Re: [VOTE] Release Apache Log4j Kotlin API 1.3.0

+1 -- The Apache Software Foundation V.P., Data Privacy On Thu, Sep 28, 2023, at 15:26, Volkan Yazıcı wrote: > This is a vote to release the Apache Log4j Kotlin API 1.3.0. > > Source repository: https://github.com/apache/logging-log4j-kotlin > Commit: b273cfb450898f079d2fd10b575330bfb900101b >

Re: `chainsaw` vs `logging-chainsaw`

Hi, Infra archived this repo for us: https://github.com/apache/chainsaw Kind regards, Christian On Fri, Sep 22, 2023, at 22:33, Gary Gregory wrote: > On Fri, Sep 22, 2023 at 2:28 PM Christian Grobmeier > wrote: >> >> >> >> On Fri, Sep 22, 2023, at 20:16, Gary Gre

Re: Archiving `logging-log4j-server` and `-audit`

Hi, what is the purpose of log4j-server actually? I don't find any information about it. I wonder, if this has a real use case (Gary uses it) but no releases, should we create a Sandbox/Lab? Personally, if this just for example purposes, we maybe should actually move it -samples as suggested

Re: [chainsaw] Trouble starting it at all

me with Netbeans and OpenJDK 11. I would expect an > exception/stack trace to be printed to stderr if an exception was thrown > that caused it to fail to load. > > -Robert Middleton > > On Fri, Sep 29, 2023 at 9:17 AM Christian Grobmeier > wrote: > >> Hi, >> >

Re: [chainsaw] Trouble starting it at all

.getBoolean("toolbar")); toolBar.setSelected(false); //configureTabPlacement(config.getInt("tabPlacement")); configureTabPlacement(1); Looks like the missing configuration is a problem. Is there any configuration I should add to the startup? On Fri, Sep 29, 2023, at 18:36, Christian Grob

Re: Refining product feature set strategy

On Mon, Oct 2, 2023, at 17:38, Ralph Goers wrote: >>> Agreed. Sandbox could be open even for all ASF committers, entry barriers >>> could be low. Dormant components could go back to sandbox as well, if new >>> people want to work on it. >> >> Can we create a repo open to all Apache

Re: [chainsaw] What is necessary for a 2.2 release?

atever). > > -Robert Middleton > > On Mon, Oct 2, 2023 at 6:12 AM Christian Grobmeier > wrote: > >> >> On Mon, Oct 2, 2023, at 02:55, Robert Middleton wrote: >> > Some(most?) of the settings should be saved: >> > >> https://githu

Re: [chainsaw] What is necessary for a 2.2 release?

being reverted, but will do what I can to > minimize the impact. Of course, I can re-refactor later ;-) Looking forward to it, feel free to revert whatever you think is necessary/makes your life easier > > Scott > > On 10/2/23, Christian Grobmeier wrote: >> On Mon, Oct 2, 20

Re: [chainsaw] What is necessary for a 2.2 release?

l keep trying to extracting things, making classes a bit smaller if possible. I will closely follow what you are doing and try to learn from it. Maybe, once we can persist tab settings and then release it, no matter how the rest of the cleanup is. > > Scott > > On 10/1/23, Christia

Re: [chainsaw] What is necessary for a 2.2 release?

I side(so you can know how things are routed) and on >> the back-end side(to do the actual routing). >> >> -Robert Middleton >> >> On Sun, Oct 1, 2023 at 3:14 PM Christian Grobmeier >> wrote: >> >>> On Sun, Oct 1, 2023, at 20:59, Scott Deboy w

Re: [chainsaw] What is necessary for a 2.2 release?

ink thats a great idea. I will be very busy for the next week, so I am not going to make many changes then. However, when I return I plan to work further on the LogPanel and cut it into pieces, so it is (hopefully) easier to maintain. Kind regards, Christian > > On 10/1/23, Christian Grobmei

[chainsaw] What is necessary for a 2.2 release?

Hello, I am moving things around a lot. There is much refactoring that is necessary alone LogPanel had ~4500 lines of code. I believe this lot of LOCs is so complicated to understand that it prevents people from contributing - let alone Swing, but we can't change that. Apart from usual

Re: Refining product feature set strategy

Hi On Sat, Sep 30, 2023, at 00:52, Ralph Goers wrote: > Requiring hoops that must be jumped through before stuff can be > accepted is just a terrible idea. It does nothing but create a > perception that we are not open to new contributions and new > contributors. I am also against hoops, but

Re: [chainsaw] What is necessary for a 2.2 release?

stream? it seem there was an update late 2022 to address some security. Should we just re-enable it or was there other reasons too? > > -Robert Middleton > > On Sun, Oct 1, 2023 at 3:39 PM Christian Grobmeier > wrote: > >> >> On Sun, Oct 1, 2023, at 21:28, Scott Deboy wr

Re: [log4j] LOG4J2-3669 Scala API license

No idea about the origin, but our repo shows: https://github.com/search?q=repo%3Aapache%2Flogging-log4j-scala%20%20typesafehub%2Fscalalogging=code The repo here: https://github.com/typesafehub/scalalogging Points to: https://github.com/lightbend-labs/scala-logging I can see that the very old

[proposal] Create sandbox, open to all committers

Hi, I want to create a sandbox for experimental logging features and ideas. All ASF committers should be welcome to contribute and have access by default. Everybody can add their custom extensions to it and develop it further. We would collect code bases from all over the eco system on a

Re: Retire Chainsaw

On Tue, Sep 19, 2023, at 20:47, Vladimir Sitnikov wrote: > I truly do not understand why PMC suggests "all or nothing". Either > "chainsaw must be fully maintained" or "it must be nuked right away > from the website". I think this was not proposed. If we archive a project, we'd move it to a

Re: Retire Chainsaw

On Tue, Sep 19, 2023, at 20:52, Vladimir Sitnikov wrote: >> Scott, could you (or anybody else) spare time to perform the following >> maintenance tasks? > > I don't use chainsaw personally, however, I am afraid I might run into > a project that does, so I would prefer to keep docs afloat. > >

Re: Retire Chainsaw

Hi we have last commits in 2022, so there was at least a little activity. I would guess we should open "issues" for Chainsaw, and add a note on the website saying "We need help". If we don't see new people stepping up, we can still do something and announce EOL. On Tue, Sep 19, 2023, at

Re: [VOTE] Release Apache Log4j Tools 0.5.0

+1 On Fri, Sep 29, 2023, at 13:13, Volkan Yazıcı wrote: > This is a vote to release the Apache Log4j Tools 0.5.0. > > Source repository: https://github.com/apache/logging-log4j-tools > Commit: 861b03c70a76ca19408ffc8c4a77bc0c4e5e4570 > Distribution:

[chainsaw] Lots of commented code // Backwards compatibility?

Hi, Looking through the code base, I saw lots of code that is commented. Some classes (maybe because of this) are not even used anymore. I only saw one class (ChainsawViewer), which might make sense to keep. Is it OK to remove this all? Or is there a specific reason for this? Some methods are

Re: [chainsaw] Is ZeroConf support relevant?

gt; Scott > > On Fri, Sep 29, 2023, 12:24 PM Christian Grobmeier > wrote: > >> Volkan asked this question here: >> https://github.com/apache/logging-chainsaw/issues/24 >> >> I guess, since Log4j1 is EOL we can safely remove this feature, right? >>

Re: [chainsaw] Trouble starting it at all

files as chainsaw.settings.properties. These files looked incomplete. After I deleted it, it actually worked. No idea why this was created that way. > > On Fri, Sep 29, 2023, 9:49 AM Christian Grobmeier > wrote: > >> OK, got it running, after commenting those lines: >> >> //sta

[chainsaw] Is ZeroConf support relevant?

Volkan asked this question here: https://github.com/apache/logging-chainsaw/issues/24 I guess, since Log4j1 is EOL we can safely remove this feature, right?

Re: [chainsaw] What is necessary for a 2.2 release?

config files and state). >>> >>> I haven’t used Commons Configuration before, but it seems fairly >>> appropriate for this sort of thing as well. >>> >>> > On Oct 2, 2023, at 1:43 PM, Christian Grobmeier >>> > wrote: >>&g

Re: [log4j] Improving log4j security

Hello Vladimir, I am not sure if you received Piotrs message below - please let us know :) Kind regards, Christian -- The Apache Software Foundation V.P., Data Privacy On Thu, Oct 5, 2023, at 22:05, Piotr P. Karwasz wrote: > Hi Vladimir, > > On Thu, 5 Oct 2023 at 21:47, Klebanov, Vladimir >

  1   2   3   4   5   6   7   8   9   10   >