This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch fix/issue-267-use-project-files-velocity
in repository
https://gitbox.apache.org/repos/asf/maven-remote-resources-plugin.git
omit eef237c Document the .vm lookup of useProjectFiles
omit a61720c Render project .vm overrides with Velocity when
useProjectFiles is set (#267)
add 52662dc Avoid mutating project artifact versions when building
$projects (#268)
add f371fb9 Copy the snapshot artifact with ArtifactUtils.copyArtifact so
no fields are lost
new 89f44f2 Render project .vm overrides with Velocity when
useProjectFiles is set (#267)
new d3555ea Document the .vm lookup of useProjectFiles
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 (eef237c)
\
N -- N -- N refs/heads/fix/issue-267-use-project-files-velocity
(d3555ea)
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:
.../remote/AbstractProcessRemoteResourcesMojo.java | 7 ++++++-
.../resources/remote/RemoteResourcesMojoTest.java | 23 ++++++++++++++++++++++
2 files changed, 29 insertions(+), 1 deletion(-)
