Log4j Maven plugin

2023-01-01 Thread Piotr P. Karwasz
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


[VOTE] Release log4cxx 1.0.0

2023-01-01 Thread Robert Middleton
This is a vote to release log4cxx 1.0.0

Please download, test, and cast your votes on the log4j developers list.
[] +1, release the artifacts
[] -1, don't release because...

This vote will remain open for 72 hours(or more if required).

All votes are welcome and we encourage everyone to test the release,
but only Logging PMC votes are “officially” counted. As always, at
least 3 +1 votes and more positive than negative votes are required.

Changes can be found on JIRA:
https://issues.apache.org/jira/projects/LOGCXX/versions/12351043

Tag:
For a new copy do "git clone
https://github.com/apache/logging-log4cxx.git; and then "git checkout
tags/v1.0.0-RC1"
For an existing working copy, do "git pull" and then "git checkout
tags/v1.0.0-RC1"

Web site: https://logging.staged.apache.org/log4cxx/next_stable/

Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4cxx/

Building directions are on the website(under 'Development').  Note
that APR is required to build(as well as boost if your compiler does
not support C++17).

-Robert Middleton