This is an automated email from the ASF dual-hosted git repository.
reschke pushed a change to branch SLING-12636
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-resourceresolver.git
omit 0645b9f Revert "SLING-12636: Resource Resolver: add test coverage for
background init"
omit 9570684 SLING-12636: Resource Resolver: add test coverage for
background init - trying to make Sonar happy
add ea037cd SLING-12636: Resource Resolver: add test coverage for
background init - fix MapEntries internal state when loadVanityPaths is called
a second time
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 (0645b9f)
\
N -- N -- N refs/heads/SLING-12636 (ea037cd)
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:
.../java/org/apache/sling/resourceresolver/impl/mapping/MapEntries.java | 2 ++
.../sling/resourceresolver/impl/mapping/VanityPathMapEntriesTest.java | 1 -
2 files changed, 2 insertions(+), 1 deletion(-)
