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 name. All Logging Services repos must start with “logging-“. So you could use “logging-maven-plugins” under the assumption there may be multiple Maven plugins. More normal for plugins though is for each to be in its own repo. So “logging-location-maven-plugin” might be a decent repo name (although a bit long). Ralph > On Jan 1, 2023, at 1:59 PM, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > > Hi all, > > After successfully merging my `LogBuilder` enhancement proposals, I > have a Maven plugin ready[#], which hardcodes location information in > a class's bytecode. > > As Ralph remarks in the PR, the right place for this module is not > necessarily the `loggjing-log4j2` repository. I tend to agree with > this: the lifecycle of this plugin is not necessarily linked with > Log4j2. I have a long list of additional features I want to implement > in the near future (like migrating SLF4J, JCL and JUL bytecode to > Log4j2 API), but after that development will probably stop (apart from > some bug fixes). > > Where do you think I should upload this code? What Maven groupId should I use? > > Piotr > > [#] https://github.com/apache/logging-log4j2/pull/1147
