This is an automated email from the ASF dual-hosted git repository.
sseifert pushed a change to branch feature/SLING-13001-adapter-manager-impl-3.x
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-testing-sling-mock.git
omit 935dbee SLING-12866 - Restrict force pushes, auto-delete branches on
merge
add f8059c8 update MockAdapterManagerImpl to logic from Sling Adapter
2.2.0
add 1370139 disable deactivate method completely
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 (935dbee)
\
N -- N -- N
refs/heads/feature/SLING-13001-adapter-manager-impl-3.x (1370139)
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:
.asf.yaml | 4 -
.../testing/mock/sling/MockAdapterManagerImpl.java | 265 ++++++++-------------
.../sling/testing/mock/sling/package-info.java | 2 +-
3 files changed, 102 insertions(+), 169 deletions(-)
