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-core-2.22.2
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-jcr-registration.git
omit 84ee8a2 Bump org.apache.jackrabbit:jackrabbit-core from 2.2.9 to
2.22.2
add e928311 SLING-13013 Update to Parent 62
add ca6bb2a SLING-13013 apply spotless formatting
add c9eaba8 SLING-13013 ignore spotless code reformatting commit in git
blame
add 4528a10 Bump org.apache.jackrabbit:jackrabbit-core from 2.2.9 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 (84ee8a2)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.jackrabbit-jackrabbit-core-2.22.2
(4528a10)
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:
.git-blame-ignore-revs | 1 +
.sling-module.json | 5 ++
pom.xml | 25 +++----
.../registration/AbstractRegistrationSupport.java | 59 ++++++++--------
.../registration/impl/JndiRegistrationSupport.java | 78 ++++++++++++----------
.../registration/impl/RmiRegistrationSupport.java | 77 +++++++++++----------
.../sling/jcr/registration/package-info.java | 3 +-
7 files changed, 137 insertions(+), 111 deletions(-)
create mode 100644 .git-blame-ignore-revs
create mode 100644 .sling-module.json
