Hi Matt,
On Tue, 3 Oct 2023 at 18:36, Matt Sicker wrote:
>
> I’ve had this idea for many years now, and as we get closer to 3.0, it seems
> like it’s time to consider the details. We can change the default
> configuration in 3.0 without being as surprising as any other version. I
> think we co
Please, not JSON output by default.
Gary
On Tue, Oct 3, 2023, 12:57 PM Ralph Goers
wrote:
> Are you just talking about changing the current default configuration? Or
> are you envisioning having more than one somewhow?
>
> If this is just about changing the current default configuration then I
Oh right, JTL isn’t in core, but it could be!
And if we change the default layout to continue using a pattern layout, how
about some colors and such like how Spring Boot defaults?
And yes, multiple default configurations was another idea I had, but I wasn’t
sure how to phrase that.
> On Oct 3,
Are you just talking about changing the current default configuration? Or are
you envisioning having more than one somewhow?
If this is just about changing the current default configuration then I have
some concerns:
1. It always has to work.
2. It cannot rely on optional components. JsonTempl
+1
Same comment about the `mvnw` script not being executable. The README could
perhaps be updated with build instructions in the future.
> On Oct 3, 2023, at 4:13 AM, Volkan Yazıcı wrote:
>
> This is a vote to release the Apache Log4j Kotlin API 1.3.0 (RC2).
>
> Website: https://logging.stage
+1
I should note that the included `mvnw` script is not executable in the zip.
> On Oct 3, 2023, at 3:29 AM, Volkan Yazıcı wrote:
>
> This is a vote to release the Apache Log4j Tools 0.5.0 (RC2).
>
> Website: https://logging.staged.apache.org/log4j/tools
> GitHub: https://github.com/apache/log
I’ve had this idea for many years now, and as we get closer to 3.0, it seems
like it’s time to consider the details. We can change the default configuration
in 3.0 without being as surprising as any other version. I think we could use
this as an opportunity to demonstrate some best practices and
+0
I don’t see the value of creating a new repo for people to contribute to. If
someone has a new idea they can create their own GitHub repo and tell us about
it. If we like it we can fork it into our own repo.
Obviously, releases would never be performed out of such a repo. That means any
cod
On Tue, 3 Oct 2023 at 11:13, Volkan Yazıcı wrote:
>
> This is a vote to release the Apache Log4j Kotlin API 1.3.0 (RC2).
>
> Website: https://logging.staged.apache.org/log4j/kotlin
> GitHub: https://github.com/apache/logging-log4j-kotlin
> Commit: 56197c6809fef293832539481b9fdbea0fc3d323
> Distrib
Sounds like it will be messy to deal with IMO, especially with any
committer allowed to do anything. GitHub PRs seems to already provide all
of the infrastructure we need. I must be missing something.
-0
Gary
On Tue, Oct 3, 2023, 4:51 AM Christian Grobmeier
wrote:
> Hi,
>
> I want to create a
Hi Christian,
On Tue, 3 Oct 2023 at 10:51, Christian Grobmeier wrote:
> I am hesitating making this an official vote, since some of us may not have
> seen this proposal buried in the other threads. However, if there is no
> negative response to this thread, I will move forward and request a git
This is a vote to release the Apache Log4j Kotlin API 1.3.0 (RC2).
Website: https://logging.staged.apache.org/log4j/kotlin
GitHub: https://github.com/apache/logging-log4j-kotlin
Commit: 56197c6809fef293832539481b9fdbea0fc3d323
Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-kotl
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
Hi Volkan,
On Tue, 3 Oct 2023 at 10:29, Volkan Yazıcı wrote:
> Please download, test, and cast your votes on this mailing list.
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
I checked:
* the source archive for the reproducibility of the build,
* the git commit for repro
This is a vote to release the Apache Log4j Tools 0.5.0 (RC2).
Website: https://logging.staged.apache.org/log4j/tools
GitHub: https://github.com/apache/logging-log4j-tools
Commit: 540cbd7dfa97cf26dc83717f738d26ee9a6b6e22
Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
Nexus
I am cancelling this vote (due to reasons stated in the thread) and
will issue an RC2 promptly.
On Thu, Sep 28, 2023 at 3:26 PM 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: b27
I am cancelling this vote (due to reasons stated in the thread) and
will issue an RC2 promptly.
On Fri, Sep 29, 2023 at 1:13 PM 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: 861b03c70
Apache Logging Parent team is pleased to announce the 10.1.1
release. This project contains the parent POM for other Maven-based
Apache Logging Services projects. For further information (support,
download, etc.) see the project website[1].
[1] https://logging.apache.org/logging-parent
=== Releas
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 Mon, Oct 2, 2023 at 11:22 AM Volkan Yazıcı wrote:
>
> This is a vote to release the Apache Logging Parent 10.1.1.
>
> Source repository: https://github.com/apach
19 matches
Mail list logo
