This is an automated email from the ASF dual-hosted git repository.
khmarbaise pushed a change to branch CODE-IMPROVEMENTS
in repository https://gitbox.apache.org/repos/asf/maven-artifact-transfer.git.
discard fdf72a7 Removed outcommented code.
add 8000df6 [MSHARED-742] - Add null check for DependencyResolver
Interface o Added missing check of ProjectBuildingRequest parameter
add 87d6c19 [maven-release-plugin] prepare release
maven-artifact-transfer-0.10.0
add d66d750 [maven-release-plugin] prepare for next development iteration
add 61e262e [MSHARED-743] - Improve documentation about install project
add 1fae4db [MSHARED-753] - Remove updateReleaseInfo from ProjectDeployer
docs
new 42978d4 Removed outcommented code.
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 (fdf72a7)
\
N -- N -- N refs/heads/CODE-IMPROVEMENTS (42978d4)
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 | 6 ++----
.../dependencies/resolve/internal/DefaultDependencyResolver.java | 2 ++
.../maven/shared/transfer/project/deploy/ProjectDeployer.java | 3 +--
src/site/apt/install-project.apt | 3 +--
4 files changed, 6 insertions(+), 8 deletions(-)
