This is an automated email from the ASF dual-hosted git repository.
pkarwasz pushed a change to branch fix/generalize-di-usage
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
omit 0c3b74b9c1 Revert changes to methods used by Spring Boot
omit 7dcc0c5b99 Revert `LogEventWrapper` changes
omit 1fd4a5ffec Revert `ConfigurationFactory` renaming
omit 64f37b6d23 Generalize DI usage
add e18403a619 Fix `PropertiesUtil` source
add 35c0f02012 Generalize DI usage
add c2b121dc19 Revert `ConfigurationFactory` renaming
add a75bd17047 Revert `LogEventWrapper` changes
add 68e22a7428 Revert changes to methods used by Spring Boot
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (0c3b74b9c1)
\
N -- N -- N refs/heads/fix/generalize-di-usage (68e22a7428)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../log4j/kit/env/internal/PropertiesUtilPropertyEnvironment.java | 2 +-
.../log4j/kit/env/internal/PropertiesUtilPropertyEnvironmentTest.java | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
