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] 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 t

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 hav

Re: log4php update

27;t found a solution (if 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/LOGGINGLO

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: [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: Your project website

Hi, I see there is some activity on the site - I discovered log4php and the audit component are currently 404. the links look correct, it seems as the sites are not at their location. Christian On Tue, Sep 1, 2020, at 03:24, Robert Middleton wrote: > Something is funny with logging.apache.org -

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: 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. Her

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 e

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

ady have 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 >&g

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: 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 log4j2

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 no

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 jus

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://gith

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 commun

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 that

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

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 shows there were commits up to >> > sometime in 2012, all of which were performed by G

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 made

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

he 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

> -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 fil

[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 t

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 dutie

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 P

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 bas

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: [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 co

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: > >

[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: [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 >> softw

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 n

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

>> > more receptive to accepting it back and making a release, 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

[log4j] Performance comparsion

Hi, found this: https://www.sitepoint.com/which-java-logging-framework-has-the-best-performance/?utm_content=buffer79511&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer

Re: [log4j] Performance comparsion

and what I wanted to write before hitting "send" to early: I think Stephen is right with saying we need to improve the docs. Log4j1 docs were bad, 2 is much better, but I think we can do much, much better. On Thu, Apr 13, 2017, at 20:38, Christian Grobmeier wrote: > Hi, > >

Re: [log4j] Performance comparsion

> > > > > > 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 > > wrote: > > >> > > >> Hi, > > >

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 > > wrote: > > > >

Re: Feedback request

I agree with Matt. What I love is the way you use annotations. I can't tell you how I miss annotations when I work with PHP. On Sat, Apr 15, 2017, at 17:47, Matt Sicker wrote: > It looks pretty neat! The single source code file idea is an amusing > C-like > distribution mechanism, but it makes

Re: [LAZY][VOTE] Release Logging parent pom version 8

+1 (first release vote in ages :-)) On Thu, Mar 2, 2023, at 22:10, Piotr P. Karwasz wrote: > This is a lazy vote to release logging-parent 8. This vote is open for > 72 hours and will pass unless getting a net negative vote count. > > Release notes: > > * The version of 'org.apache:apache' has b

Re: [External] Re: Log4j Issue

Hello Gurumoorthi, Piotr already responded to your email: > MapLookup#newMap changed from private (as in 2.2) to package (as in > 2.17.1) in the course of history. Your Tomcat is picking up the > private one, which means that log4j-core-2.2.jar is still on the > classpath. > Double check that the

Re: [External] Re: Log4j Issue

am wrote: > Any help on this request ? we stuck. > > -Original Message- > From: Gurumoorthi Vijayalingam > Sent: Thursday, April 13, 2023 7:36 AM > To: Christian Grobmeier ; dev@logging.apache.org > Subject: RE: [External] Re: Log4j Issue > > Hi Team, > &g

Re: [External] Re: Log4j Issue

The problem > occurred when we upgraded the jar files from 2.2 t o2.17 > > > Regards, > Guru. > > -Original Message- > From: Christian Grobmeier > Sent: Friday, April 21, 2023 4:36 PM > To: Gurumoorthi Vijayalingam ; > dev@logging.apache.org >

Re: [External] Re: Log4j Issue

ar 2 17:28 log4j-api-2.17.1.jar > -rwxr-xr-x. 1 fruser fruser 1790452 Mar 2 17:28 log4j-core-2.17.1.jar > > Regards, > Guru. > > -Original Message- > From: Christian Grobmeier > Sent: Friday, April 21, 2023 4:55 PM > To: Gurumoorthi Vijayalingam ; > de

Future of our websites

Hello, I want to discuss the future of our logging websites and have prepared a document for that: https://cwiki.apache.org/confluence/display/LOGGING/The+future+of+Logging+websites+and+social+media We have the opportunity to work with a designer, too. For now, I'd like to collect your ideas on

Remove Noise: using commits@?

Should Github notifications go to a separate list? I know there will be changes regarding threading for these kind of notifications, but maybe we should just use comm...@logging.apache.org for Github stuff?

Re: Remove Noise: using commits@?

gs 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 thi

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 >> https://repository.apache.org/content/repositories/orgapachelog

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: https://dist.apache.org/repos/dist/dev/logg

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 dor

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. > > Vol

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 20:45

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 will

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 wil

Re: `chainsaw` vs `logging-chainsaw`

gt; 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 >>

[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 In

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 Jekyl

Re: Migrating the landing page

lso GUI support 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,

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: `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 be

Re: Migrating the landing page

o on. The rest – converting >> these into HTML pages, 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 >>

Re: Migrating the landing page

gt; styling. In my opinion, ideally, projects should simply 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 th

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 > Di

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 t

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

[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 org.apa

Re: [chainsaw] Trouble starting it at all

te: > It starts up for 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: >

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 Grobmeie

Re: [chainsaw] Trouble starting it at all

les 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] 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: [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: https://dist.apache.org/repos/dist/dev/logging

[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

[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 refacto

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

e code more comprehensible. I will 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. > > S

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

equires a bit more >> planning on both the UI 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: >> >>

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

I think 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 Gr

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

em 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 wrote:

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 a

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

r whatever). > > -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://

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

oring 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,

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 committer

[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 centra

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&type=code The repo here: https://github.com/typesafehub/scalalogging Points to: https://github.com/lightbend-labs/scala-logging I can see that the very ol

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 > wr

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

XStream for managing 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 >>> &g

[all] Sonarcloud

Hi, I added a fork of Chainsaw to Sonarcloud, which I find very helpful: https://sonarcloud.io/summary/overall?id=grobmeier_logging-chainsaw I asked Infra, and they would add projects by request to Sonarcloud. If you are interested, I'd like to add that to our repos. If not, it is fine because

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

iven the desire to avoid Java >> >>> serialization, it is perfectly reasonable to avoid XStream as that’s >> >>> basically Java serialization using XML with all the pitfalls that >> entails >> >>> (I dealt with this fairly extensively back in the Je

Re: [log4j] Improving log4j security

Since Piotrs response went to spam (thanks for confirming) I'd like to make sure you reveived Volkans questions as well. Please let me know if you did. If you didn't, he sent his response to the mailing list, if you need help subscribing, please let me know On Mon, Oct 9, 2023, at 22:28, Volk

Status of log4j-audit

Hello, We have been talking about log4j-audit (same thread as with log4j-server). I have checked today after seeing Piotr's message, and even after reading the readme, I am still trying to figure out the purpose of this product. That aside, I am concerned the last change was four years ago. -au

[site] Jekyll proposal (in branch)

Hello, Based on recent comments, I made a branch for using Jekyll on the leading site. It's a branch, we can discard it. The migration took me 1.5h, excluding this e-mail - not much wasted. https://github.com/apache/logging-site/tree/jekyll This is not yet auto-deployed, but if nobody opposes

Re: Status of log4j-audit

estion, I’d expect that if we adopt Flume into the >> PMC, then Flume would supersede the server examples since we’d have >> something far more mature and production-ready for such a use case. >> >>> On Oct 10, 2023, at 1:33 PM, Christian Grobmeier >>> wrote: >&g

Re: [site] Jekyll proposal (in branch)

, I'd like to move this to asf-site Kind regards, Christian On Tue, Oct 10, 2023, at 23:10, Christian Grobmeier wrote: > Hello, > > Based on recent comments, I made a branch for using Jekyll on the > leading site. It's a branch, we can discard it. The migration took me >

Re: [log4j] Improving log4j security

This whole problem sounds as follows: - we don't escape because we don't think we should use a pattern layout like this - an attacker sends data to the log - the log sends data to a processing system - if this processing issue has a flaw, bad things might happen It does not sound like a widespre

Re: [log4j] Improving log4j security

On Thu, Oct 12, 2023, at 20:44, Piotr P. Karwasz wrote: > However we should consider properly documenting PatternLayout: there > should be a warning reminding users that while it is technically > possible to generate a proper JSON or XML using this layout it is not > the suggested way. No object

[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: https://reposit

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 `asf-stagi

  1   2   >