This is an automated email from the ASF dual-hosted git repository.
khmarbaise pushed a change to branch MNG-6391
in repository https://gitbox.apache.org/repos/asf/maven.git.
discard b047f0a [MNG-6391] - Printout version of last built module in reactor
build
add 6e619a1 [MNG-6496] Upgrade Maven Resolver to 1.3.1
add 42c77a7 Repair Jenkins job - add a full path to workspace when run on
Windows
new 23f5c88 [MNG-6391] - Printout version of last built module in reactor
build
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 (b047f0a)
\
N -- N -- N refs/heads/MNG-6391 (23f5c88)
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:
Jenkinsfile | 4 ++--
maven-resolver-provider/pom.xml | 9 ++++++++
.../internal/DefaultArtifactDescriptorReader.java | 24 +---------------------
.../internal/DefaultVersionRangeResolver.java | 22 +-------------------
.../internal/DefaultVersionResolver.java | 22 +-------------------
pom.xml | 2 +-
6 files changed, 15 insertions(+), 68 deletions(-)
