+1 Remko
On Tue, Jan 3, 2023 at 4:57 PM Thorsten Schöning
wrote:
> Guten Tag Robert Middleton,
> am Sonntag, 1. Januar 2023 um 19:06 schrieben Sie:
>
> > Please download, test, and cast your votes on the log4j developers list.
> > [] +1, release the artifacts
> > [] -1, don't release because...
I disagree with putting these into `logging-log4j-tools` with the current
state of the project: It is intended for *internal* usage. For
`log4j-changelog`, I want to make it explicit that it is not intended for
usage outside Log4j itself. I have two proposals:
1. Create a new `logging-log4j-inf
That sounds like a great sweet spot to settle on. We can periodically
(hourly?) run a GitHub Actions workflow that checks if all `release-2.x`
commits older than 24 hours have a subject-matching counterpart in `master`
(and vice versa), if not, creates a GitHub Issue assigned to the author of
the c
Sounds like it could backfire in some cases creating busy work: What
happens when I commit to 2.x for code that has been deprecated or removed
in 3.x? Certainly we don't want to create tickets for those. Do I have to
remember to put a special comment in the commit message?
Gary
On Tue, Jan 3, 202
I assume such cases to be relatively infrequent. If not, we can introduce a
commit message magic word to disarm the mechanism. All in all, is clicking
on the _Close_ button of a ticket really that difficult?
Note that these tickets would also constitute a good historical account for
hinting the di
I don’t necessarily object to this version of the proposal. While not perfect
it should eliminate most of the noise.
Ralph
> On Jan 3, 2023, at 2:01 AM, Volkan Yazıcı wrote:
>
> That sounds like a great sweet spot to settle on. We can periodically
> (hourly?) run a GitHub Actions workflow that
Hi Volkan,
On Tue, 3 Jan 2023 at 09:45, Volkan Yazıcı wrote:
>1. Create a new `logging-log4j-infra` (groupId: `o.a.l.l.infra`)
>repository and move the `log4j-changelog` module there and put Piotr's
>stuff into `logging-log4j-tools` (groupId: `o.a.l.l.tools`)
>2. Move everybody to
ppkarwasz opened a new pull request, #23:
URL: https://github.com/apache/logging-log4j1/pull/23
Helps automatic detecting the security policy that applies to Log4j 1.2
(i.e. end-of-life), but using an established file name.
--
This is an automated message from the Apache Git Service.
To r
`logging-log4j-transform` and `org.apache.logging.log4j` are fine by me.
On Tue, Jan 3, 2023 at 6:43 PM Piotr P. Karwasz
wrote:
> Hi Volkan,
>
> On Tue, 3 Jan 2023 at 09:45, Volkan Yazıcı wrote:
> >1. Create a new `logging-log4j-infra` (groupId: `o.a.l.l.infra`)
> >repository and move t
+1
I have built and tested the .zip archive using Visual Studio 2019.
I tested the .taz.gz archive with gcc 9.4 on Ubuntu
On Tue, Jan 3, 2023 at 7:37 PM Remko Popma wrote:
> +1 Remko
>
> On Tue, Jan 3, 2023 at 4:57 PM Thorsten Schöning
> wrote:
>
> > Guten Tag Robert Middleton,
> > am Sonntag
I do like this as a separate repo. If I understand what you are intending I
expect that releasing this tool will be big news:
1. It automatically converts calls to SLF4J to Log4j, eliminating the need to
include the SLF4J and log4j-slf4j-impl jars at runtime.
2. It adds location information for f
11 matches
Mail list logo
