This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a change to branch MARTIFACT-74
in repository https://gitbox.apache.org/repos/asf/maven-artifact-plugin.git
omit a0dbd4c [MARTIFACT-74] describe groupId(s) and duplicate artifactId(s)
add e181b9e [MARTIFACT-74] describe groupId(s) and duplicate artifactId(s)
add e59fc49 [MARTIFACT-74] add describe-build-output IT
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 (a0dbd4c)
\
N -- N -- N refs/heads/MARTIFACT-74 (e59fc49)
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:
.../invoker.properties | 2 +-
.../modA-other-groupId}/pom.xml | 3 +-
.../modA/pom.xml | 0
.../it/describe-multi/modA/src/main/java/Foo.java | 8 +++--
.../modB/pom.xml | 0
.../modSkipDeploy/pom.xml | 0
src/it/{buildinfo-multi => describe-multi}/pom.xml | 35 ++--------------------
.../buildinfo/DescribeBuildOutputMojo.java | 12 ++++----
8 files changed, 19 insertions(+), 41 deletions(-)
copy src/it/{check-buildplan-ok => describe-multi}/invoker.properties (90%)
copy src/it/{buildinfo-multi/modA =>
describe-multi/modA-other-groupId}/pom.xml (91%)
copy src/it/{buildinfo-multi => describe-multi}/modA/pom.xml (100%)
copy Jenkinsfile => src/it/describe-multi/modA/src/main/java/Foo.java (86%)
copy src/it/{buildinfo-multi => describe-multi}/modB/pom.xml (100%)
copy src/it/{buildinfo-skip-install-deploy =>
describe-multi}/modSkipDeploy/pom.xml (100%)
copy src/it/{buildinfo-multi => describe-multi}/pom.xml (68%)
