Re: [VOTE] Release Apache Log4net 3.0.4

+1 I checked as far as I could, and it looks good to me -- The Apache Software Foundation V.P., Data Privacy On Mon, Feb 17, 2025, at 18:18, Jan Friedrich wrote: > This is a vote to release the Apache Log4net 3.0.4. > > Website: > https://logging.staged.apache.org/log4net/release/release-notes.h

Re: Successor to mailing lists

t; > must end up recorded on Apache-owned resources, which GH is not. >> > > > >> > > > Gary >> > > > >> > > > On Thu, Oct 10, 2024 at 7:07 AM Apache >> > wrote: >> > > > >> > > > > I cannot express an opinion wi

[RESULT] [VOTE] Move Flume to dormant

dormant section of the website and adding a note to the README. As mentioned, codebase will stay writable for now, this is just for informing our users. Kind regards, Christian -- The Apache Software Foundation V.P., Data Privacy - Original message - From: Christian Grobmeier To: dev

Re: Successor to mailing lists

Hi I am generally open to such experiments. I would start with the easiest parts, such as users@, and see where it goes. I would advise against mirroring it to users@ behind the scenes, as it may cause privacy problems (we need user consensus to mirror it). When a user uses GitHub, they know

Re: [VOTE] Move Flume to dormant

On Thu, Oct 3, 2024, at 18:10, Gary Gregory wrote: > FWIW, I don't think apache voting guidelines allow for "you can only vote a > certain way only if ..." That's why I wrote: "Please CONSIDER voting ONLY -1, if:" Cheers, Christian > > Gary > >

[VOTE] Move Flume to dormant

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 don't regret moving it into Logging Services, but we have not seen any significant movement. This message (private, please don't quote from it), on the other hand, is si

Re: [log4cxx] Release time?

If you got a bunch of things, go for it. I am huge fan of „release early, often“ On Fri, Sep 27, 2024, at 01:17, Robert Middleton wrote: > Is there anything that people are looking for in a new release? We've > got a good bunch of changes ready, so I figure it's about time to do a > new release.

Re: [VOTE] Release Apache Log4net 3.0.1

+1 It looks good to me, thanks for the hard work -- The Apache Software Foundation V.P., Data Privacy On Tue, Sep 24, 2024, at 21:48, Jan Friedrich wrote: > This is a vote to release the Apache Log4net 3.0.1. > > Website: > https://logging.staged.apache.org/log4net/release/release-notes.html >

Re: [VOTE] Release Apache Log4net 3.0.0

On Mon, Sep 16, 2024, at 15:49, Jan Friedrich wrote: > Hi Gary, > > please see https://lists.apache.org/thread/v8kyxz7zdvp3cypo1506yflk3bbvysym > > I did not change the subject to [RESULT]. This is just a formality which I doubt anyway 😂 probably it comes from the times when we are actually se

Re: Use RTC in Log4j and Log4Net

Hello, After working on Log4j with PRs, I have changed my opinion on CTR/RTC in this case. Previously, I would have said keep CTR. However, I worked with RTC using PRs, and my experiences were not bad. I was a bit lost with the comments on the PR, but I figured it out somehow. I think GitHub is

Re: [VOTE] Release Apache Log4j `2.24.0`

On Tue, Sep 3, 2024, at 21:51, Gary Gregory wrote: > From my point of view, building has gotten worse and less reliable over > time :-( To be fair, the new build system was, at least for me, welcoming and straightforward to use. Although complex under the hood, it’s a major improvement over th

Re: [VOTE] Release Apache Log4j Kotlin API `1.5.0` RC1

Hi, I did what Piotr did, and the formalities seem all good. +1 Thanks for the work! Christian -- The Apache Software Foundation V.P., Data Privacy On Tue, Aug 6, 2024, at 12:47, Piotr P. Karwasz wrote: > Hi Volkan, > > On Sat, 3 Aug 2024 at 19:23, Volkan Yazıcı wrote: >> Please download, tes

Re: Updating the Logging Services Logo

On Tue, Jul 23, 2024, at 14:20, Gary Gregory wrote: > Hi. My view is do nothing until we get a new official logo. You don't want > to create any branding confusion IMO. There is no confusion by removing a feather. Come on, seriously not. One of the feathers is stands alone. It feels like „I don

Re: Updating the Logging Services Logo

On Tue, Jul 23, 2024, at 13:39, Gary Gregory wrote: > Don't create and use a new Apache logo without Apache marketing involved > (or whichever part of Aapche is doing this). > We didn’t involve marketing before. Why skittle we involve anyone by just removing the feather from the main site? This

Re: Updating the Logging Services Logo

is nothing to do wir approbation and does not need any change. Again, I want to remove feathers. > Ralph > >> On Jul 22, 2024, at 12:58 PM, Gary Gregory wrote: >> >> I find it peculiar that ALL feathers are now illegal. What about the >> feather of a Phoenix? >&

Re: Updating the Logging Services Logo

024, 3:37 PM Christian Grobmeier > wrote: > >> I am only asking to remove native american imagery as the feathers. >> As I was involved in the branding process, I am confident we can remove >> them. >> >> We can update the 1980-style logo after the ASF logo w

Re: Updating the Logging Services Logo

fore 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 G

Re: Updating the Logging Services Logo

Btw, here is a more official blog post on this change: https://news.apache.org/foundation/entry/evolving-the-asf-brand On Mon, Jul 22, 2024, at 21:32, Christian Grobmeier wrote: > I am only asking to remove native american imagery as the feathers. > As I was involved in the branding process

Updating the Logging Services Logo

Hello, following this blog post: https://news.apache.org/foundation/entry/evolving-the-asf-brand I would like to propose to remove all feathers as here: https://logging.apache.org/ https://logging.apache.org/log4j/2.x/images/ls-logo.jpg And all sub-websites with simlar images. I would like to m

Re: [Log4j] Potential support/dev policy for plugins

+1 Sounds like a good thing. Being in the top 8% of most critical open source projects requires us to consider everything very carefully I also see that we need to adopt the Airflow requirements to us a bit, but they are indeed a very good start -- The Apache Software Foundation V.P., Data Pri

Re: Release timeline for 2.24.0

On Sat, May 25, 2024, at 04:22, Gary Gregory wrote: > 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. Me too. I feel that all the discussion on the ScopedContext should be in an experimental branch or an

Re: [VOTE] Release Apache Log4j Tools 0.8.0 (RC2)

+1, tested as before On Tue, Mar 19, 2024, at 12:34, Volkan Yazıcı wrote: > This is a vote to release the Apache Log4j Tools 0.8.0 (RC2). > > Website: https://logging.staged.apache.org/log4j/tools > GitHub: https://github.com/apache/logging-log4j-tools > Commit: 2bb07037bbbfe14fe1c224d46a3e4135b

Re: [VOTE] Release Apache Log4j Tools 0.8.0

+1 Did the same checks as Piotr. Thanks for the work! On Mon, Mar 18, 2024, at 23:04, Piotr P. Karwasz wrote: > Hi Volkan, > > On Mon, 18 Mar 2024 at 22:25, Volkan Yazıcı wrote: >> >> This is a vote to release the Apache Log4j Tools 0.8.0. >> >> Website: https://logging.staged.apache.org/log4j/t

Re: [VOTE] Release Apache Log4Net 2.0.17

+1 Checked only formalities since I don't have an idea about .NET, but so far, looks good! On Sat, Mar 16, 2024, at 11:07, Volkan Yazıcı wrote: > +1 > > Checked sigs, hashes, `LICENSE` files, and release notes. > > > > On Fri, Mar 15, 2024 at 1:29 PM Davyd McColl wrote: >> >> Hi all, >> >> Thi

Re: [RESULT][VOTE] Move Chainsaw to dormant

I have moved Chainsaw to the dormant section on the main website: https://logging.apache.org/ There is a label missing on the CS website itself, but I will have similar work in future, so I am going to do it together with that On Fri, Feb 16, 2024, at 09:56, Christian Grobmeier wrote: >

Re: Please update Flume DOAP

Thank you Sebb, I just fixed it https://github.com/apache/logging-flume/commit/692039032ce681c3a847847365f0065608eae4e2 On Thu, Mar 7, 2024, at 12:42, sebb wrote: > https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf > still shows the PMC as Flume; please update to show PMC Logging.

[RESULT][VOTE] Move Chainsaw to dormant

The vote succeeded with 7 +1. Thanks to everybody who voted. I will do the necessary steps early next week. Kind regards Christian -- The Apache Software Foundation V.P., Data Privacy - Original message - From: Christian Grobmeier To: dev@logging.apache.org Subject: [VOTE] Move

Re: Move Chainsaw to dormant: Q

On Tue, Feb 13, 2024, at 05:09, Tim Perry wrote: > Do dormant projects clearly indicate they can be re-animated by a > sufficient number of active committers? In the case of Chainsaw and Log4php, I don't see any issues with it, and if people are willing to maintain it (not only short-term fixes)

[VOTE] Move Chainsaw to dormant

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 better to move Chainsaw to the dormant section and communicate it as "no longer m

[chainsaw] Status change?

Hello we have had Chainsaw for a long time in our product list, and I can totally see that some - myself included - are emotionally attached to it. However, due to my work on it, I have given it some additional thought. After working with the Chainsaw code base for a while, I saw that many feat

Re: [VOTE] Release Apache Log4j Scala 13.1.0

Did basic checks only, but +1 On Mon, Feb 5, 2024, at 21:53, Piotr P. Karwasz wrote: > Hi Volkan, > > On Thu, 1 Feb 2024 at 11:32, Volkan Yazıcı wrote: >> >> This is a vote to release the Apache Log4j Scala 13.1.0. >> >> Website: https://logging.staged.apache.org/log4j/scala >> GitHub: https:/

Week 51 in Log4j

Hello This is already the last update for this year :) Have a few great days ahead! Christian Ongoing work • Website structure & tooling exploration • Recyclers Completed work • log4j-jctools module in main • First part of plugin doc & XSD auto-generation completed: https://github.com/apa

Re: [log4j] Revamping Log4j website & manual tooling

On Wed, Dec 20, 2023, at 17:50, Volkan Yazıcı wrote: > On Wed, Dec 20, 2023 at 5:05 PM Christian Grobmeier > wrote: > >> I see only one mention of Antora, the tool you are proposing. > > > I am indeed **not** proposing Antora (removed its mentions), but plain > AsciiDo

Re: [log4j] Revamping Log4j website & manual tooling

I see only one mention of Antora, the tool you are proposing. You don't have to sell us Asciidoc; we all have our opinions about it; the majority of the document is about "why not" but little "why Antora" I would be more interested in the challenges/benefits of Antora, and how such a system cou

Re: [VOTE] Release Apache Log4j 3.0.0-beta1

Hi On Tue, Dec 19, 2023, at 21:14, Christian Grobmeier wrote: > Hi Ralph > > On Tue, Dec 19, 2023, at 16:20, Ralph Goers wrote: >> The vote has been open for 6 days because we were under the impression >> the vote was going be cancelled based on Piotr’s feedback. I can com

Re: [VOTE] Release Apache Log4j 3.0.0-beta1

ft on his plate). Could you help out as a release manager in case he can't? Generally, spreading the knowledge of releasing using the new toy is a good idea. Christian > Ralph > >> On Dec 19, 2023, at 6:12 AM, Christian Grobmeier >> wrote: >> >> Hi Volkan &g

Re: [VOTE] Release Apache Log4j 3.0.0-beta1

Hi Volkan On Tue, Dec 19, 2023, at 13:43, Volkan Yazıcı wrote: > I am cancelling this vote. I may try to issue an RC2 this week if time > allows. If you think that is inconvenient due to upcoming xmas, and/or you > want to issue the RC2 yourself, please let me know. please don't cut an RC2 this w

20 years of Log4j: Happy anniversary folks!

Happy anniversary, folks! Yesterday, on 17.12.2003, the ASF accepted our project, and Log4j was born. Twenty years later, this community is not only vibrant but growing. I have met many great people in this project and continue to learn from our user base, committers, and PMC members. Therefo

[weekly] Week 50 in Log4j

Hello everybody, I hope you're all doing well. As some of you might have noticed, we've been busy over the past few months. I want to ensure everyone's on the same page about what we've achieved and where we're heading. I chose this weekly update format to ensure inclusivity, especially conside

Re: Versioning scheme

On Tue, Dec 12, 2023, at 09:43, Volkan Yazıcı wrote: > I agree with Ralph's view. It is not just the *view* in itself that I find > appealing, but the (practically) deterministic nature of it. If one would > closely look at Robert's and/or Piotr's explanation of patch-vs-minor > strategy, it is pre

Re: Versioning scheme

Hi Volkan, I am not sure what you are proposing. On Mon, Dec 11, 2023, at 10:26, Volkan Yazıcı wrote: > I propose embracing a common versioning scheme across all Logging Services > projects; log4j, log4cxx, etc. As you already mentioned, except for some parts of Log4j 1, we are following serve

Re: [flume] Website upgrade? (building the current site fails)

On Sat, Dec 9, 2023, at 17:30, Ralph Goers wrote: > Did you follow the instructions at > https://cwiki.apache.org/confluence/display/FLUME/Updating+the+Web+Site? > I don’t know why it would be using Sphinx 1.1.2. Yes, I was failing at step 4 (mvn package) I think, it is the underlying Python

[flume] Website upgrade? (building the current site fails)

Hi, I work with flume-site, which uses Sphinx. Unfortunately, I cannot build the site because of the message below. A quick search gave me this issue: https://github.com/prestodb/presto/issues/3849 I am assuming now that Sphinx does not support mkdirs on my system (Mac). Digging deeper, I saw t

Re: Future release schedule

Hi Piotr, I think scheduled releases that everybody can follow are great and your proposal makes sense. Does this also mean we don't have that many "noise" emails from upgraded dependency (releases)? I have come to realize in the past months that "inclusion" is most important, and that would

[chainsaw] Question: oading/writing settings of ChainsawTabbedPane

Hi, I re-added the load/write feature in ChainsawTabbedPane using JSON and Genson: https://github.com/apache/logging-chainsaw/blob/master/src/main/java/org/apache/log4j/chainsaw/components/tabbedpane/ChainsawTabbedPane.java#L126-L191 If it works, I will refactor it further so we can reuse the wri

Re: [Flume] Integration with OpenTelemetry

On Thu, Nov 30, 2023, at 18:04, Matt Sicker wrote: > Oh yes, I’d still love to see how we can adapt the Log4j plugin system > here! And yeah, this would likely make sense as its own repository. > I’ll make a proposal about the OTel stuff before working on any code. Please do. I would also lik

Re: [chainsaw] Next steps? Or is it over?

t use a simple format for now: >> MESSAGE >> >> tailing: >> true >> >> * Click OK >> >> A new tab with the receiver name - default is 'Receiver' - will be >> created and entries from the log file will be routed there. >> >>

Re: [chainsaw] Next steps? Or is it over?

functionality was never added to log4j2. > > Remote tailing via the VFSLogFilePatternReceiver, with the existing > filter and search support, is enough I think. > > I'll jump in and help. > > Scott > > Scott > > On 11/28/23, Christian Grobmeier wrote: >&g

[chainsaw] Next steps? Or is it over?

Hello, I have started to clean up a few things that seemed good to me. The last time I sent a message like this was 1.5 months ago, but there was not much progress in maintaining it. I am currently in a state where I slowly get what should be happening, but unfortunately, it does not. We are n

Re: Disable new issues in JIRA

We could try something like this: https://github.com/hbrands/jira-issues-importer Both projects have APIs... -- The Apache Software Foundation V.P., Data Privacy On Fri, Nov 24, 2023, at 19:37, Matt Sicker wrote: > I’d like it if we could copy over open issues to GH. > — > Matt Sicker > >> On No

Re: [log4j] Unstable tests on Windows

Ralph said, nobody would ever fix these tests if you do it like this. I think you should create the ticket but keep the tests until we find the issue. Otherwise there issues will rot On Wed, Nov 22, 2023, at 09:13, Volkan Yazıcı wrote: > AFAIC, nobody[1] shows a strong opposition against the ide

Re: [VOTE] Release Apache Log4j Tools 0.6.0

Should the SBOM/CycloneDX files be part of the distribution folder as well? https://dist.apache.org/repos/dist/dev/logging/log4j-tools/ On Wed, Nov 15, 2023, at 16:03, Volkan Yazıcı wrote: > This is a vote to release the Apache Log4j Tools 0.6.0. > > Website: https://logging.staged.apache.org/log

Re: [log4j] What is JPMS support and its state

On Tue, Nov 7, 2023, at 15:05, Matt Sicker wrote: > I’m not going to backport the DI system. It relies on Java 11 in all > sorts of random places, first of all. I had to update numerous plugins > and tests along the way, especially things that set up or manipulate > static state, much of whic

Re: Deterministic formatter

On Wed, Nov 8, 2023, at 09:04, Volkan Yazıcı wrote: > I completely agree with Matt. With or without IDE plugins, we run `./mvnw > spotless:apply` anyway. Hence, lack of Eclipse support is not a blocker, > IMO. Gary is covered. > > +1 deterministic formatter (don't have an opinion on Palantir-vs-

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 exactly a

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

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: Why is JNDI still necessary?

r 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

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 concerns

Re: Why is JNDI still necessary?

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?

t; not a functional 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 th

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 compa

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

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 norm

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 > I'

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 I

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

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

en when we rollback, there will not be a change, as we already have tzhe old setup > > > On Fri, Oct 13, 2023 at 1:47 PM Christian Grobmeier > wrote: > >> >> >> [1] Christian's recent Jekyll experiment on the `asf-staging` branch >> >> of `loggin

Re: Staging sites and repo convention

On Sun, Oct 22, 2023, at 21:54, Volkan Yazıcı wrote: > It has been a long thread and I want to capture the result: *there are no > objections to Piotr's proposal, right?* If not, please say so. I am not objecting, but I would like to point out that logging.s.a.o is in bad shape today, and I do

Re: [log4j] Project URLs per major version

This sounds pretty cool Volkan, if I didn't get anything I pretty much like it. One question - you wrote: "we all will enjoy automatically populated Log4j websites." Does this mean we will see our website is updated automatically by CI so we can see in example /log4j/dev? Or what else is "automa

Re: Staging sites and repo convention

>> It would mean "use logging.staged.apache.org (the ~), but generate the >> content to the subfolder /log4j". >> I left out the magic /content folder since it was a given. This magic folder >> appears to be the problem that I raised with moving the main site to >> logging, at least, that's wh

Re: [audit] Versioning goals

On Sat, Oct 21, 2023, at 01:02, Ralph Goers wrote: >> On Oct 20, 2023, at 2:38 PM, Christian Grobmeier >> wrote: >> >> Hi, >> >> i just tried to run mvn test/compile etc on audit and wow, i think its a lot >> of work. >> >> What is the

[audit] Versioning goals

Hi, i just tried to run mvn test/compile etc on audit and wow, i think its a lot of work. What is the target jdk version? It seems as Java 17 already causes lots of trouble, even with Java 11 I run into issues, if I looked correctly. At least, this code base does not seem to run on newer VMs

Re: Staging sites and repo convention

On Fri, Oct 20, 2023, at 18:43, Ralph Goers wrote: > If I am reading this correctly that would mean we want all our projects > to have an empty profile so that they all appear under > logging.staged.apache.org and > logging.apache.org

Re: Staging sites and repo convention

On Fri, Oct 20, 2023, at 09:03, Piotr P. Karwasz wrote: > On Fri, 20 Oct 2023 at 07:55, Ralph Goers wrote: >> As far as the worktree stuff goes, I’d be in favor of that if it can be used >> to solve the issues Piotr mentions where Log4j-Scala and Log4j-Kotlin need >> to be independently committe

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 been

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

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 s

Re: [VOTE][LAZY] Release Apache Logging Parent 10.2.0

+1 On Wed, Oct 18, 2023, at 21:54, Volkan Yazıcı wrote: > This is a lazy-vote to release the Apache Logging Parent 10.2.0. > > Website: https://logging-parent.staged.apache.org/logging-parent > GitHub: https://github.com/apache/logging-parent > Commit: 13ee5ca880ef515b69fb1fc6b5fe2e1807e48be6 > Di

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

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

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

nsawEventBatchListener objects). >> I'm not sure how best to let the user hook things up - some sort of >> visual programming/flow-based view would be very cool but also very >> complicated. >> >> -Robert Middleton >> >> On Mon, Oct 9, 2023 at 3:24 PM C

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

[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

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

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

[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

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

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

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

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

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

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

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

  1   2   >