Hi Ralph,
On Wed, 4 Jan 2023 at 01:42, Ralph Goers wrote:
> 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:
At least I hope it will be big news, previous attempts like SLF4J
Migrator[1] do not seem to be very popula
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
`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
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
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
I think putting it in the tools repo would be fine.
Ralph
> On Jan 2, 2023, at 2:34 PM, Piotr P. Karwasz wrote:
>
> Hi,
>
>> On Mon, 2 Jan 2023 at 10:08, Volkan Yazıcı wrote:
>> Agreed with the separate repository idea. I suggest moving it to the
>> `logging-log4j-maven-plugins` repository –
Hi,
On Mon, 2 Jan 2023 at 10:08, Volkan Yazıcı wrote:
> Agreed with the separate repository idea. I suggest moving it to the
> `logging-log4j-maven-plugins` repository – you need an INFRA ticket to
> create the repository.
The Maven plugin will not be the only use-case of the code after I
finish
Link to the self-service page: https://selfserve.apache.org/
—
Matt Sicker
> On Jan 2, 2023, at 09:31, Ralph Goers wrote:
>
> The groupId will almost always be “org.apache.logging.log4j” unless it isn’t
> specifically for log4j. In that case the last token would be the
> “category/subproject”
The groupId will almost always be “org.apache.logging.log4j” unless it isn’t
specifically for log4j. In that case the last token would be the
“category/subproject” it belongs to.
As far as where to put it you have a few choices. Any PMC member can create a
new repo so the only question is the n
Great job, Piotr! 👏
Agreed with the separate repository idea. I suggest moving it to the
`logging-log4j-maven-plugins` repository – you need an INFRA ticket to
create the repository.
If we go that route, I strongly suggest incorporating following goodies
from the `logging-log4j-tools` repository:
10 matches
Mail list logo
