I see what you did with the annotation processor. I figured I’d be able to
add more metadata in the service class generated basically. If we can
identify the various logical scopes in the library, I think that could lead
to less potential bugs.
On Sun, Nov 3, 2019 at 14:14 Ralph Goers wrote:
> I
I have a couple of comments:
It isn’t really possible for me to know what you are suggesting without seeing
some examples of how plugins would be defined.
I have a suspicion the scopes could get nasty. Some plugins would be tied to
the LoggerContext, which essentially has a lifetime of the Class
Oh, almost forgot to mention my other main goal here: I have a
hypothesis that if designed our APIs with inversion of control in
mind, programmatic configuration and extension should be _much_ easier
to support while maintaining backward compatibility, too. While the
configuration framework itself
Hi Shubham Jain,
welcome to this mailing list. Plese consider subscribing to avoid future
manual interventions by a human moderator.
The application works with consoleappender enabled when run from console.
This indicates to me that the issue is related to the environment in
headless mode. The sy
Dear log4cxx developers,
I was packaging the most recent commit of log4xx (014954db) into a
tarball. But to clearly identify the tarball, I modified the `AC_INIT'
setting of `configure.ac' like below:
AC_INIT([apachelog4cxx], [0.10.0-603-014954db])
The resulting tarball after `make dist' was
Hi,
I am facing issue when trying to use both RollingFileAppender and
ConsoleAppender in .net core log4net. We are launching a console
application (.net core 3.0) from apache server. When we are launching the
application from command prompt then everything works fine but when we
launch the applica
