Excellent — thank you!
--
Jim Wise
jw...@draga.com
> On Dec 31, 2021, at 13:05, Juan Pablo Santos Rodríguez
> wrote:
>
> Hi Jürgen,
>
> in order to ease file logging, last push adds an (unused) rolling file
> appender with
Hi Jürgen,
in order to ease file logging, last push adds an (unused) rolling file
appender with some sensible defaults. This way, to enable file logging
it'd only be needed to add the reference to the logger, f.ex.,
something like:
rootLogger.appenderRef.rolling.ref = RollingFile
in the
This config below in jspwiki-custom.properties works for me now, at
least it writes the log, will see in some days, if it indeed rolls.
Unfortunately log4j2 chose not to have a common prefix and thus a
namespace for their property names, so it is kind of messy.
# Give directory path where log
Hi Jim,
for a quick check, I set up the log level to debug and saw the file with
contents (I did the test with the cargo maven plugin, but that shouldn't
matter).
Would you mind trying that? If you also have the log redirected to the
stdout, do you see log there? Also, setting status=debug on
Does this work for you?
I have this config (albeit with a different fileName), and while the files are
created, they do not receive any log messages.
--
Jim Wise
jw...@draga.com
> On Dec 17, 2021, at 16:31, Juan Pablo Santos
Hi Jürgen,
there's a commented section on the jspwiki.properties file setting up
a rolling appender for the security log. The default configuration
should be the same as before, translated from the equivalent log4j1
configuration that was in place. With that example, the following
works for me:
Finally found some time to update to 2.11.0.
Experience was mixed.
Had to port my plugins to the changed API (kind of frivolous to change
the API of a mature product, I dare to say, and break all existing
plugins), but this went rather smoothly.
But I didn't get the new logging to work. Do I
