This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch MINVOKER-267
in repository https://gitbox.apache.org/repos/asf/maven-invoker-plugin.git.
discard 428d195 [MINVOKER-267] script-interpreter 1.3
discard 76939cf [MINVOKER-267] Update maven-script-interpreter to next
release version
add dfd3c36 (doc) Clarify behavior for maven-plugin project (#26)
new 8ebd1c5 [MINVOKER-267] Update maven-script-interpreter to 1.3
new 9f4d423 [MINVOKER-267] Update BeanShell to 2.0b6 (sync with
script-interpreter)
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 (428d195)
\
N -- N -- N refs/heads/MINVOKER-267 (9f4d423)
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 | 11 -----------
.../org/apache/maven/plugins/invoker/AbstractInvokerMojo.java | 2 ++
src/site/apt/examples/clone-projects.apt.vm | 2 ++
3 files changed, 4 insertions(+), 11 deletions(-)
