You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ol...@apache.org on 2020/10/18 23:30:10 UTC

[maven-invoker-plugin] branch master updated: (doc) Clarify behavior for maven-plugin project (#26)

This is an automated email from the ASF dual-hosted git repository.

olamy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-invoker-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new dfd3c36  (doc) Clarify behavior for maven-plugin project (#26)
dfd3c36 is described below

commit dfd3c3680f31cb36ef1c14c18f4ea8b8d6115151
Author: Piotrek Żygieło <pz...@users.noreply.github.com>
AuthorDate: Mon Oct 19 01:30:02 2020 +0200

    (doc) Clarify behavior for maven-plugin project (#26)
---
 src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java | 2 ++
 src/site/apt/examples/clone-projects.apt.vm                             | 2 ++
 2 files changed, 4 insertions(+)

diff --git a/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java b/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java
index ee088ad..cf1d7e5 100644
--- a/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java
+++ b/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java
@@ -186,6 +186,8 @@ public abstract class AbstractInvokerMojo
      * Directory to which projects should be cloned prior to execution. If set to {@code null}, each integration test 
      * will be run in the directory in which the corresponding IT POM was found. In this case, you most likely want to
      * configure your SCM to ignore <code>target</code> and <code>build.log</code> in the test's base directory.
+     * (<b>Exception</b> when project using invoker plugin is of <i>maven-plugin</i> packaging:
+     * In such case IT projects will be cloned to and executed in <code>target/its</code> by default.)
      *
      * @since 1.1
      */
diff --git a/src/site/apt/examples/clone-projects.apt.vm b/src/site/apt/examples/clone-projects.apt.vm
index 0c52bff..4dfd456 100644
--- a/src/site/apt/examples/clone-projects.apt.vm
+++ b/src/site/apt/examples/clone-projects.apt.vm
@@ -29,6 +29,8 @@
 Cloning Projects
 
   By default the projects will be executed in the same directory where they are found.
+  (With the exception when project using invoker plugin is of <maven-plugin> packaging.
+  In such case IT projects will be cloned to and executed in <<<target/its>>> by default.)
   This means that build output will be generated with the project files.  It may be
   helpful to copy the projects to another directory before running them, for example
   <<<target/it>>>.  This will allow <<<mvn clean>>> to remove the output generated