This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.jackrabbit-jackrabbit-jcr-commons-2.22.2
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-jcr-resource.git
omit 8a2e4d0 Bump org.apache.jackrabbit:jackrabbit-jcr-commons from 2.18.0
to 2.22.2
add df83378 SLING-12940 read userData only for local events (#48)
add 2c6375b [maven-release-plugin] prepare release
org.apache.sling.jcr.resource-3.3.4
add 98c759c [maven-release-plugin] prepare for next development iteration
add feb6da9 Bump org.apache.jackrabbit:jackrabbit-jcr-commons from 2.18.0
to 2.22.2
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 (8a2e4d0)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.jackrabbit-jackrabbit-jcr-commons-2.22.2
(feb6da9)
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:
pom.xml | 4 ++--
.../jcr/resource/internal/JcrResourceListener.java | 18 +++++++++---------
2 files changed, 11 insertions(+), 11 deletions(-)
