This is an automated email from the ASF dual-hosted git repository.
sjaranowski pushed a change to branch MPLUGIN-495
in repository https://gitbox.apache.org/repos/asf/maven-dependency-plugin.git
omit 5b114b7b Fix all Unit Tests
omit 4c2f56b0 Fix one test
omit 4b7b8abb Use @Component only
add 2cf89f44 Bump org.jsoup:jsoup from 1.17.1 to 1.17.2 (#361)
add f0929217 Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2 (#359)
add 0c1baf7c Bump org.codehaus.plexus:plexus-archiver from 4.9.0 to 4.9.1
(#358)
add 5389514f Bump apache/maven-gh-actions-shared from 3 to 4
add 1948d276 Bump org.codehaus.plexus:plexus-archiver from 4.9.1 to 4.9.2
add 4a4999ff [MDEP-912] Use version for plexus-utils/plexus-xml from parent
add 572cebbc Use default configuration for GitHub Actions
add b4703b2d Use @Component only
add 957528cb Fix one test
add fd39ca8a Fix all Unit Tests
add 4e181ee8 Add todo to remove with next parent
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 (5b114b7b)
\
N -- N -- N refs/heads/MPLUGIN-495 (4e181ee8)
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:
.github/workflows/maven-verify.yml | 4 +---
pom.xml | 14 +++++++++-----
2 files changed, 10 insertions(+), 8 deletions(-)
