Hi Volkan, On Tue, 3 Jan 2023 at 09:45, Volkan Yazıcı <vol...@yazi.ci> 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 their own repo: `logging-log4j-changelog`, > `logging-log4j-instrument`, `logging-log4j-errorprone`, etc. This might > turn out to be a better approach given aforementioned projects will most > probably have totally different development cycles.
What about `logging-log4j-transform`? The Maven plugin could be called `log4j-transform-maven-plugin` in case we publish other plugins. For the groupId I think `org.apache.logging.log4j` that Ralph proposes will be fine. Piotr
