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: - GitHub Actions `build.yml` (the repository path there needs to be adapted) - `/pom.xml` + `log4j-tools-parent/pom.xml` (Note that you need neither a `-bom`, nor a `-parent` module! Adding sources to the root module should suffice.) - `CHANGELOG.adoc` - `LICENSE.txt` - `SECURITY.adoc` - `spotless-license-header.txt` - `.editorconfig` - `.asf.yaml` (`github.description` needs to be updated here) - `.gitignore` - `.java-version` I put a great deal of effort into their correctness and compactness, hence my insistence on reusing them. On Sun, Jan 1, 2023 at 10:00 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 >
