This is an automated email from the ASF dual-hosted git repository.
jsedding pushed a change to branch
fix/SLING-12019-duplicate-ResourceResolverFactory-registration
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-resourceresolver.git
discard 57eddc5 SLING-12019 - Avoid duplicate ResourceResolverFactory
registrations
discard c0b50ee Merge remote-tracking branch 'origin/master' into
fix/SLING-12019-duplicate-ResourceResolverFactory-registration
discard b7be02a SLING-12019 - Avoid duplicate ResourceResolverFactory
registrations
discard 96eb560 SLING-12019 - Avoid duplicate ResourceResolverFactory
registrations
discard eb0d3ea SLING-12019 - Avoid duplicate ResourceResolverFactory
registrations
add bbdc147 SLING-12019 - Avoid duplicate ResourceResolverFactory
registrations
add d31b0ff SLING-12019 - Avoid duplicate ResourceResolverFactory
registrations
add 705aab8 SLING-12019 - Avoid duplicate ResourceResolverFactory
registrations
add 02ab2eb SLING-12019 - Avoid duplicate ResourceResolverFactory
registrations
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 (57eddc5)
\
N -- N -- N
refs/heads/fix/SLING-12019-duplicate-ResourceResolverFactory-registration
(02ab2eb)
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:
.../sling/resourceresolver/impl/MockedResourceResolverImplTest.java | 2 ++
1 file changed, 2 insertions(+)
