This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.codehaus.plexus-plexus-archiver-4.8.0
in repository
https://gitbox.apache.org/repos/asf/sling-feature-converter-maven-plugin.git
omit 465b15c Bump org.codehaus.plexus:plexus-archiver from 3.5 to 4.8.0
add adeac11 SLING-12094 - Use GitHub for the Maven scm.url value
add cc007d8 SLING-12459 - Redirect sonarcloud notifications to
[email protected]
add cfacb3c SLING-12715 - feature-converter-maven-plugin Jenkins buid
fails
add 53f5a29 SLING-12715 - feature-converter-maven-plugin Jenkins buid
fails
add 80c32d9 SLING-12715 - feature-converter-maven-plugin Jenkins buid
fails
add bc7c76c SLING-12715 - feature-converter-maven-plugin Jenkins buid
fails
add 1eae314 Merge pull request #10 from apache/issue/SLING-12715
add 7e3f93a Bump org.codehaus.plexus:plexus-archiver from 3.5 to 4.8.0
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 (465b15c)
\
N -- N -- N
refs/heads/dependabot/maven/org.codehaus.plexus-plexus-archiver-4.8.0 (7e3f93a)
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 | 1 +
.sling-module.json | 7 ++++++
pom.xml | 29 +++++++++++++++++++---
.../core/pom.xml | 4 ---
.../core/pom.xml | 6 +----
.../core/pom.xml | 4 ---
src/it/setup-tests/pom.xml | 2 +-
7 files changed, 36 insertions(+), 17 deletions(-)
create mode 100644 .sling-module.json
