maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From khmarba...@apache.org
Subject [maven-dependency-plugin] branch MDEP-625 updated (23bb997 -> ed40304)
Date Sat, 15 Dec 2018 10:59:06 GMT
This is an automated email from the ASF dual-hosted git repository.

khmarbaise pushed a change to branch MDEP-625
in repository https://gitbox.apache.org/repos/asf/maven-dependency-plugin.git.


 discard 23bb997  Added https TLSv1.2
 discard 0ca0e1b  [MDEP-625] - Upgrade maven-artifact-transfer to 0.10.0
     add 068d3cd  [MDEP-634] - Upgrade plexus-io to 3.1.0
     add ef4f5b6  [MDEP-636] - Upgrade maven-shared-utils 3.2.1
     add 7962db7  Removed deprecated call.
     new 20bd14d  [MDEP-625] - Upgrade maven-artifact-transfer to 0.10.0
     new ed40304  Added https TLSv1.2

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   (23bb997)
            \
             N -- N -- N   refs/heads/MDEP-625 (ed40304)

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 2 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                                                               | 4 ++--
 .../org/apache/maven/plugins/dependency/AbstractDependencyMojo.java   | 2 --
 2 files changed, 2 insertions(+), 4 deletions(-)


Mime
View raw message