This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a change to branch doxia-2.0.0
in repository https://gitbox.apache.org/repos/asf/maven-dependency-plugin.git
omit fa132e73 [MDEP-903] Upgrade to Doxia 2.0.0 Milestone Stack
add 94e1caf5 Bump org.jsoup:jsoup from 1.17.2 to 1.18.1
add 86b77724 (doc) Remove repeated word
add 2d0b82a8 Bump org.codehaus.plexus:plexus-io from 3.4.2 to 3.5.0
add ea4d8e24 Bump jettyVersion from 9.4.54.v20240208 to 9.4.55.v20240627
add 5288cece Bump org.apache.maven.plugins:maven-plugins from 42 to 43
add 1115ecb4 Bump org.codehaus.plexus:plexus-archiver from 4.9.2 to 4.10.0
new 50397c42 [MDEP-903] Upgrade to Doxia 2.0.0 Milestone Stack
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 (fa132e73)
\
N -- N -- N refs/heads/doxia-2.0.0 (50397c42)
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:
pom.xml | 24 +++++++++++++++++-----
.../checkstyle-suppressions.xml} | 21 ++++++-------------
src/site/apt/index.apt.vm | 2 +-
3 files changed, 26 insertions(+), 21 deletions(-)
copy src/{test/resources/unit/get-test/repository/test/test/1.0/test-1.0.pom
=> config/checkstyle-suppressions.xml} (61%)
