You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's currently possible to use URLs to load Log4j2 configuration. In Spring Boot 2.x we opened these URLs directly, but it would be better if we used Log4j2 mechanisms so that properties such as log4j2.trustStoreLocation are respected.
The text was updated successfully, but these errors were encountered:
* pr/32578:
Document Log4j2 extensions
* Merge pull request for #32735:
Polish 'Resolve URLs using Log4J2 mechanisms'
Resolve URLs using Log4j2 mechanisms
* Merge pull request for #32734:
Polish 'Support profile specific Log4j2 configuration'
Support profile specific Log4j2 configuration
* Merge pull request for #32733:
Polish 'Add Log4J2 PropertySource backed by the Spring Environment'
Add Log4J2 PropertySource backed by the Spring Environment
* Merge pull request for #32732:
Polish 'Support Log4J2 string lookups from the Spring Environment'
Support Log4J2 string lookups from the Spring Environment
* Merge pull request for #32730:
Polish 'Add Spring Environment to LoggerContext'
Add Spring Environment to LoggerContext
* Merge pull request for #32730:
Polish 'Support 'log4j.configurationFile' system property'
Support 'log4j.configurationFile' system property
Closesgh-32578
It's currently possible to use URLs to load Log4j2 configuration. In Spring Boot 2.x we opened these URLs directly, but it would be better if we used Log4j2 mechanisms so that properties such as
log4j2.trustStoreLocation
are respected.The text was updated successfully, but these errors were encountered: