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
discard 348a7e2 SLING-13212: Add LogStoreListener that allows reading of the
logs on a push-based API
add 666528b SLING-13212: Expose more structured information about
exceptions
add 9b5eb24 Add LogEntryListener that allows reading of the logs on a
push-based 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 (348a7e2)
\
N -- N -- N refs/heads/logstore-extensions (9b5eb24)
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:
.../log/logback/internal/store/LogStoreImpl.java | 10 ++--
.../logback/internal/store/LogStoreRegistrar.java | 64 +++++-----------------
...LogStoreListener.java => LogEntryListener.java} | 2 +-
.../commons/log/logback/store/package-info.java | 2 +-
.../integration/ITLogStoreRegistrarLifecycle.java | 45 +--------------
.../logback/internal/store/LogStoreImplTest.java | 6 +-
6 files changed, 26 insertions(+), 103 deletions(-)
rename
src/main/java/org/apache/sling/commons/log/logback/store/{LogStoreListener.java
=> LogEntryListener.java} (97%)
