This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to branch issue/SLING-7935
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-starter.git
discard 43ae45e Document workaround for bnd-indexer-maven-plugin issue
discard 0829dc8 TEST: add a dummy mirror repository to the CI profile
discard 59b3a75 TEST: run Maven build with debug output
discard d8c1f65 TEST: downgrade test-fragment to version 12
discard 8048a8a SLING-7935 - Move launchpad-testing module into the main
starter repository
add ed0b4b7 Update to o.a.s.j.j.usermanager v2.20.0 and related
dependencies
add 05fe7f7 Update composum to version 4.1.1
add 565b0be Update to Models API 1.4.2, Models Implementation 1.5.2
add 650f585 Update to o.a.s.j.j.usermanager v2.2.22
add 359ac80 SLING-7935 - Move launchpad-testing module into the main
starter repository
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 (43ae45e)
\
N -- N -- N refs/heads/issue/SLING-7935 (359ac80)
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-module.json | 3 +--
pom.xml | 2 +-
src/main/features/base.json | 10 +++++-----
src/main/features/oak/oak_base.json | 2 +-
src/main/features/scripting.json | 2 +-
src/main/features/test/test-content.json | 2 +-
6 files changed, 10 insertions(+), 11 deletions(-)
