Hey great - yeah I'll go through and add some tickets.
The event routing mechanism is very simple - you define an expression
using the logging event attribute names, and the values in the logging
event are used to convert that expression into a concrete tab name,
where the events are routed.
For those of you who didn't see on slack: I did update Chainsaw last
night so you can load/save receivers. That brings Chainsaw back into
a usable state(in my mind at least). I need to check to ensure that
everything gets saved properly, but that shouldn't be too hard.
Scott, would you mind
Nevermind. I was using the wrong url.
Ralph
> On Oct 13, 2023, at 8:21 AM, Ralph Goers wrote:
>
> I get a 404 trying to access the log4j2 staging web site. Although
> technically not required for a release I am not comfortable voting for the
> release without being able to see the web site.
I get a 404 trying to access the log4j2 staging web site. Although technically
not required for a release I am not comfortable voting for the release without
being able to see the web site.
Ralph
> On Oct 13, 2023, at 6:46 AM, Piotr P. Karwasz wrote:
>
> Hi Christian,
>
> On Fri, 13 Oct
I am getting a 404 trying to access https://logging.staged.apache.org.
Ralph
> On Oct 12, 2023, at 9:16 AM, Christian Grobmeier wrote:
>
> Hello,
>
> I made the Jekyll branch work with the staging environment:
> https://logging.staged.apache.org/
>
> When you change something in the sources,
Hi Christian,
On Fri, 13 Oct 2023 at 13:46, Christian Grobmeier wrote:
> Why is content not causing this issue?
> For me both is possible, just trying to understand the best way.
>From what I understand, if a branch (in any repo) has a configuration:
staging:
whoami: name_of_the_branch
vy merged PR #1:
URL: https://github.com/apache/logging-log4j-jmx-gui/pull/1
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
The current version is certainly way simpler than before, I liked it.
I agree with moving every "data" (members, projects, etc.) to its own data file.
I still prefer all typesetting performed in AsciiDoc. (I am not
telling you to do so immediately. But that is where I'd like this
initiative to
Apache Log4j Scala team is pleased to announce the 13.0.0
release. This project provides a Scala-friendly interface to log
against the Log4j API. For further information (support, download,
etc.) see the project website[1].
[1] https://logging.apache.org/log4j/scala
=== Release Notes
The
Adding my +1.
With that, the release passes with 3 binding +1 votes from Piotr,
Matt, and me. I will continue the release process.
On Tue, Oct 10, 2023 at 1:21 PM Volkan Yazıcı wrote:
>
> This is a vote to release the Apache Log4j Scala 13.0.0.
>
> Website:
>> [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
Hi all,
On Fri, 13 Oct 2023 at 12:16, Volkan Yazıcı wrote:
>
> ✔ Binaries
> ✔ Sources
> ✔ Website (incl. Javadocs)
> Ă Website URL[1]
> ✔ Signatures
> ✔ Checksums
>
> +1
Same here:
* the binaries in the binary archive, Maven repo and locally
generated are identical. Somehow `log4j-perf` made
✔ Binaries
✔ Sources
✔ Website (incl. Javadocs)
Ă Website URL[1]
✔ Signatures
✔ Checksums
+1
Thanks for taking care of the release Christian!
[1] Christian's recent Jekyll experiment on the `asf-staging` branch
of `logging-site` repository confused the INFRA and it is acting
strangely. This
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:
14 matches
Mail list logo
