This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to branch issue/SLING-12475
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-feature-cpconverter.git
discard 28bdcc1 SLING-12475 - Remove test-only usage of GSON
omit 30507b2 SLING-12475 - Remove test-only usage of GSON
add 25593d2 SLING-12475 - Remove test-only usage of GSON (#181)
add 7294a8f SLING-12476 - Remove JDK and OS limitations from CPConverter
build (#182)
add 3da475b SLING-12477 - Bump commons-io:commons-io from 2.11.0 to
2.14.0 (#178)
add 1819ca3 chore(docs): adjust documentation with regards to supported
repoinit structures.
new 085101d SLING-12475 - Remove test-only usage of GSON
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 (28bdcc1)
\
N -- N -- N refs/heads/issue/SLING-12475 (085101d)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.sling-module.json | 6 ------
README.md | 7 +------
pom.xml | 2 +-
3 files changed, 2 insertions(+), 13 deletions(-)
delete mode 100644 .sling-module.json
