This is an automated email from the ASF dual-hosted git repository.
royteeuwen pushed a change to branch logstore-extensions
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-commons-log.git
omit b8af0c8 Address review: keep package API backwards compatible and
harden listener API
omit 9b5eb24 Add LogEntryListener that allows reading of the logs on a
push-based API
omit 666528b SLING-13212: Expose more structured information about
exceptions
add e80b2d1 SLING-13224 - Allow configuring which loggers the LogStore
captures
add f6c8c8c Address review: simplify logger config handling
add ed0f17e Merge pull request #34 from apache/SLING-13224
add 220505c SLING-13212: Expose more structured information about
exceptions
add c1881b2 Add LogEntryListener that allows reading of the logs on a
push-based API
add ba21360 Address review: keep package API backwards compatible and
harden listener API
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 (b8af0c8)
\
N -- N -- N refs/heads/logstore-extensions (ba21360)
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:
.../logback/internal/store/LogStoreRegistrar.java | 33 ++++++++++++++++--
.../integration/ITLogStoreRegistrarLifecycle.java | 39 ++++++++++++++++++++++
2 files changed, 69 insertions(+), 3 deletions(-)
