I have updated the PR with some documentation:
- Global settings page re-ordered with headings matching the user
interface
- Added references to individual settings for better cross linking
- Live examples of the logging profiles.
One interesting discovery was how log4j handles our
Feedback from last week's meeting has been accounted for, and after
days/weeks the PR https://github.com/geoserver/geoserver/pull/5734 is
passing tests and QA checks locally!
I would like to issue a release candidate Wednesday, in order to collect
feedback from our user community with respect to
I got feedback via https://issues.apache.org/jira/browse/LOG4J2-3469 that
what I am doing is safe, but not in the spirit of Log4J2 (which is external
control focused, preventing a lot of applications from updating).
The offered a slightly prettier way to things, but I still do not like it
(my ow
Andrea:
I reached out to the log4j community
https://issues.apache.org/jira/browse/LOG4J2-3469
This took a long time to write up, but doing so kind of confirmed for me
that I am using the API as they intended. The "Node" data structure is what
their builder infrastructure produces (either parsin
I can run an experiment, but logback was also very much configuration up
front and under external control attitude (which is not a bad attitude to
be honest).
Jody
On Wed, Apr 6, 2022 at 1:08 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:
> Hi Jody,
> silly question maybe, but did yo
Hi Jody,
silly question maybe, but did you try to reach out to the Log4J2 community
and see if there
is a less painful way to do it?
Being able to change the log config without restarts is key to the day to
day management of GeoServer.
Otherwise, maybe we can look into Logback (75% kidding here)
