Reconfiguring already is a fast and robust operation. But if you have
status=“debug” enabled it is a little disconcerting to see it configure 4 times.
Ralph
> On Oct 9, 2019, at 11:49 AM, Matt Sicker wrote:
>
> If we made reconfiguring a fast and robust operation, there’d be nothing
> wrong wi
If we made reconfiguring a fast and robust operation, there’d be nothing
wrong with that approach.
On Wed, Oct 9, 2019 at 13:41, Ralph Goers
wrote:
> I am sure we could, but I am not sure how that helps the usage in Spring.
>
> Another thought would be to have Log4j reconfigure when it finally h
I am sure we could, but I am not sure how that helps the usage in Spring.
Another thought would be to have Log4j reconfigure when it finally has access
to a configuration in the application.yaml, but that would mean configuring
Log4j a 4th time.
Ralph
> On Oct 9, 2019, at 11:12 AM, Matt Sicke
Can we provide a log4j configuration facade API for doing common
programmatic configuration tasks like that? Think Configurator but for
manipulating certain aspects of a Configuration that's already
running.
On Wed, 9 Oct 2019 at 12:49, Ralph Goers wrote:
>
> Recently I added support for Spring C
Recently I added support for Spring Cloud Config to Log4j. In an effort to
continue to persuade Spring to use Log4j as the default Logging implementation
I would like to consider other ways we could improve our Spring integration.
The problem is, I am not really sure what that would be.
Curre
