Modified: maven/website/components/plugins-archives/maven-invoker-plugin-LATEST/run-mojo.html ============================================================================== --- maven/website/components/plugins-archives/maven-invoker-plugin-LATEST/run-mojo.html (original) +++ maven/website/components/plugins-archives/maven-invoker-plugin-LATEST/run-mojo.html Mon Jun 23 21:49:14 2025 @@ -2,7 +2,7 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 2.0.0 from org.apache.maven.plugins:maven-plugin-report-plugin:3.13.1:report at 2024-12-06 + | Generated by Apache Maven Doxia Site Renderer 2.0.0 from org.apache.maven.plugins:maven-plugin-report-plugin:3.15.1:report at 2025-06-23 | Rendered using Apache Maven Fluido Skin 2.0.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> @@ -48,8 +48,8 @@ <li><a href="../index.html">Plugins</a><span class="divider">/</span></li> <li><a href="index.html">Apache Maven Invoker Plugin</a><span class="divider">/</span></li> <li class="active">invoker:run</li> - <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2024-12-06</li> - <li id="projectVersion" class="pull-right">Version: 3.9.0</li> + <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2025-06-23</li> + <li id="projectVersion" class="pull-right">Version: 3.9.1</li> </ul> </div> </header> @@ -59,7 +59,7 @@ <ul class="nav nav-list"> <li class="nav-header">Overview</li> <li><a href="index.html">Introduction</a></li> - <li><a href="plugin-info.html">Goals</a></li> + <li><a href="plugin-info.html">Plugin Documentation</a></li> <li><a href="usage.html">Usage</a></li> <li><a href="groovy-version.html">Groovy version</a></li> <li><a href="faq.html">FAQ</a></li> @@ -124,10 +124,10 @@ </div> </header> <main id="bodyColumn" class="span10"> -<section> -<h1>invoker:run</h1><a id="invoker.3Arun"></a> +<section><a id="invoker.3Arun"></a> +<h1>invoker:run</h1> <p><strong>Full name</strong>:</p> -<p>org.apache.maven.plugins:maven-invoker-plugin:3.9.0:run</p> +<p>org.apache.maven.plugins:maven-invoker-plugin:3.9.1:run</p> <p><strong>Description</strong>:</p> <p>Searches for integration test Maven projects, and executes each, collecting a log in the project directory, and outputting the results to the command line.</p> <p><strong>Attributes</strong>:</p> @@ -136,8 +136,8 @@ <li>Requires dependency resolution of artifacts in scope: <code>test</code>.</li> <li>The goal is thread-safe and supports parallel builds.</li> <li>Since version: <code>1.0</code>.</li> -<li>Binds by default to the <a class="externalLink" href="https://maven.apache.org/ref/current/maven-core/lifecycles.html";>lifecycle phase</a>: <code>integration-test</code>.</li></ul><section> -<h2>Optional Parameters</h2><a id="Optional_Parameters"></a> +<li>Binds by default to the <a class="externalLink" href="https://maven.apache.org/ref/current/maven-core/lifecycles.html";>lifecycle phase</a>: <code>integration-test</code>.</li></ul><section><a id="Optional_Parameters"></a> +<h2>Optional Parameters</h2> <table class="table table-striped"> <tr class="a"> <th>Name</th> @@ -145,72 +145,72 @@ <th>Since</th> <th>Description</th></tr> <tr class="b"> -<td style="text-align: left;"><a href="#addTestClassPath"><code><addTestClassPath></code></a></td> +<td><a href="#addTestClassPath"><code><addTestClassPath></code></a></td> <td><code>boolean</code></td> <td><code>1.2</code></td> <td>A flag whether the test class path of the project under test should be included in the class path of the pre-/post-build scripts. If set to <code>false</code>, the class path of script interpreter consists only of the <a href="dependencies.html">runtime dependencies</a> of the Maven Invoker Plugin. If set the <code>true</code>, the project's test class path will be prepended to the interpreter class path. Among others, this feature allows the scripts to access utility classes from the test sources of your project.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.addTestClassPath</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#cloneAllFiles"><code><cloneAllFiles></code></a></td> +<td><a href="#cloneAllFiles"><code><cloneAllFiles></code></a></td> <td><code>boolean</code></td> <td><code>1.2</code></td> <td>Some files are normally excluded when copying the IT projects from the directory specified by the parameter projectsDirectory to the directory given by cloneProjectsTo (e.g. <code>.svn</code>, <code>CVS</code>, <code>*~</code>, etc: see <a href="https://codehaus-plexus.github.io/plexus-utils/apidocs/org/codehaus/plexus/util/AbstractScanner.html#DEFAULTEXCLUDES";> reference</a> for full list). Setting this parameter to <code>true</code> will cause all files to be copied to the <code>cloneProjectsTo</code> directory.<br /><strong>Default</strong>: <code>false</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#cloneClean"><code><cloneClean></code></a></td> +<td><a href="#cloneClean"><code><cloneClean></code></a></td> <td><code>boolean</code></td> <td><code>1.6</code></td> <td>Ensure the <a href="#cloneProjectsTo"><code>cloneProjectsTo</code></a> directory is not polluted with files from earlier invoker runs.<br /><strong>Default</strong>: <code>true</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#cloneProjectsTo"><code><cloneProjectsTo></code></a></td> +<td><a href="#cloneProjectsTo"><code><cloneProjectsTo></code></a></td> <td><code>File</code></td> <td><code>1.1</code></td> -<td>Directory to which projects should be cloned prior to execution. If set to <code>null</code>, 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.)<br /><strong>User Property</strong>: <code>invoker.cloneProjectsTo</code></td></tr> +<td>Directory to which projects should be cloned prior to execution. If set to <code>null</code>, 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.) Note: cloning needs to be enabled for properties filtering to work.<br /><strong>User Property</strong>: <code>invoker.cloneProjectsTo</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#collectedProjects"><code><collectedProjects></code></a></td> +<td><a href="#collectedProjects"><code><collectedProjects></code></a></td> <td><code>List<String></code></td> <td><code>3.9.0</code></td> <td>Projects that are cloned undergo some filtering. In order to grab all projects and make sure they are all filtered, projects are read and parsed. In some cases, this may not be a desired behavior (especially when some pom.xml cannot be parsed by Maven directly). In such cases, the exact list of projects can be set using this field, avoiding the parsing of all pom.xml files found.</td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#debug"><code><debug></code></a></td> +<td><a href="#debug"><code><debug></code></a></td> <td><code>boolean</code></td> <td><code>1.0</code></td> <td>Whether to show debug statements in the build output.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.debug</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#disableReports"><code><disableReports></code></a></td> +<td><a href="#disableReports"><code><disableReports></code></a></td> <td><code>boolean</code></td> <td><code>1.4</code></td> <td>A flag to disable the generation of build reports.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.disableReports</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#encoding"><code><encoding></code></a></td> +<td><a href="#encoding"><code><encoding></code></a></td> <td><code>String</code></td> <td><code>1.2</code></td> <td>The file encoding for the pre-/post-build scripts and the list files for goals and profiles.<br /><strong>Default</strong>: <code>${project.build.sourceEncoding}</code><br /><strong>User Property</strong>: <code>encoding</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#environmentVariables"><code><environmentVariables></code></a></td> +<td><a href="#environmentVariables"><code><environmentVariables></code></a></td> <td><code>Map<String,String></code></td> <td><code>1.8</code></td> <td>Additional environment variables to set on the command line.</td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#failIfNoProjects"><code><failIfNoProjects></code></a></td> +<td><a href="#failIfNoProjects"><code><failIfNoProjects></code></a></td> <td><code>Boolean</code></td> <td><code>1.9</code></td> <td>Set this to <code>true</code> to cause a failure if there are no projects to invoke.<br /><strong>User Property</strong>: <code>invoker.failIfNoProjects</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#filterProperties"><code><filterProperties></code></a></td> +<td><a href="#filterProperties"><code><filterProperties></code></a></td> <td><code>Map<String,String></code></td> <td><code>1.3</code></td> <td>A list of additional properties which will be used to filter tokens in POMs and goal files.</td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#goals"><code><goals></code></a></td> +<td><a href="#goals"><code><goals></code></a></td> <td><code>List<String></code></td> <td><code>1.0</code></td> <td>The list of goals to execute on each project. Default value is: <code>package</code>.</td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#ignoreFailures"><code><ignoreFailures></code></a></td> +<td><a href="#ignoreFailures"><code><ignoreFailures></code></a></td> <td><code>boolean</code></td> <td><code>1.3</code></td> <td>A flag controlling whether failures of the sub builds should fail the main build, too. If set to <code>true</code>, the main build will proceed even if one or more sub builds failed.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>maven.test.failure.ignore</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#invokerPropertiesFile"><code><invokerPropertiesFile></code></a></td> +<td><a href="#invokerPropertiesFile"><code><invokerPropertiesFile></code></a></td> <td><code>String</code></td> <td><code>1.2</code></td> <td>The name of an optional project-specific file that contains properties used to specify settings for an individual Maven invocation. Any property present in the file will override the corresponding setting from the plugin configuration. The values of the properties are filtered and may use expressions like <code>${project.version}</code> to reference project properties or values from the parameter <a href="#filterProperties"><code>filterProperties</code></a>. @@ -341,75 +341,75 @@ invoker.updateSnapshots = true </pre><br /><strong>Default</strong>: <code>invoker.properties</code><br /><strong>User Property</strong>: <code>invoker.invokerPropertiesFile</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#invokerTest"><code><invokerTest></code></a></td> +<td><a href="#invokerTest"><code><invokerTest></code></a></td> <td><code>String</code></td> <td><code>1.1 (exclusion since 1.8)</code></td> <td>A comma separated list of projectname patterns to run. Specify this parameter to run individual tests by file name, overriding the <a href="#setupIncludes"><code>setupIncludes</code></a>, <a href="#pomIncludes"><code>pomIncludes</code></a> and <a href="#pomExcludes"><code>pomExcludes</code></a> parameters. Each pattern you specify here will be used to create an include/exclude pattern formatted like <code>${projectsDirectory}/<i>pattern</i></code>. To exclude a test, prefix the pattern with a '<code>!</code>'. So you can just type <nobr><code>-Dinvoker.test=SimpleTest,Comp*Test,!Compare*</code></nobr> to run builds in <code>${projectsDirectory}/SimpleTest</code> and <code>${projectsDirectory}/ComplexTest</code>, but not <code>${projectsDirectory}/CompareTest</code><br /><strong>User Property</strong>: <code>invoker.test</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#javaHome"><code><javaHome></code></a></td> +<td><a href="#javaHome"><code><javaHome></code></a></td> <td><code>File</code></td> <td><code>1.3</code></td> <td>The <code>JAVA_HOME</code> environment variable to use for forked Maven invocations. Defaults to the current Java home directory.<br /><strong>User Property</strong>: <code>invoker.javaHome</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#junitPackageName"><code><junitPackageName></code></a></td> +<td><a href="#junitPackageName"><code><junitPackageName></code></a></td> <td><code>String</code></td> <td><code>3.1.2</code></td> <td>The package name use in junit report<br /><strong>Default</strong>: <code>maven.invoker.it</code><br /><strong>User Property</strong>: <code>invoker.junitPackageName</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#localRepositoryPath"><code><localRepositoryPath></code></a></td> +<td><a href="#localRepositoryPath"><code><localRepositoryPath></code></a></td> <td><code>File</code></td> <td><code>1.0</code></td> <td>The local repository for caching artifacts. It is strongly recommended to specify a path to an isolated repository like <code>${project.build.directory}/it-repo</code>. Otherwise, your ordinary local repository will be used, potentially soiling it with broken artifacts.<br /><strong>Default</strong>: <code>${settings.localRepository}</code><br /><strong>User Property</strong>: <code>invoker.localRepositoryPath</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#logDirectory"><code><logDirectory></code></a></td> +<td><a href="#logDirectory"><code><logDirectory></code></a></td> <td><code>File</code></td> <td><code>3.2.0</code></td> <td>By default a <code>build.log</code> is created in the root of the project. By setting this folder files are written to a different folder, respecting the structure of the projectsDirectory.</td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#mavenExecutable"><code><mavenExecutable></code></a></td> +<td><a href="#mavenExecutable"><code><mavenExecutable></code></a></td> <td><code>String</code></td> <td><code>1.8</code></td> <td>mavenExecutable can either be a file relative to <code>${maven.home}/bin/</code>, test project workspace or an absolute file.<br /><strong>User Property</strong>: <code>invoker.mavenExecutable</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#mavenHome"><code><mavenHome></code></a></td> +<td><a href="#mavenHome"><code><mavenHome></code></a></td> <td><code>File</code></td> <td><code>1.3</code></td> <td>The home directory of the Maven installation to use for the forked builds. Defaults to the current Maven installation.<br /><strong>User Property</strong>: <code>invoker.mavenHome</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#mavenOpts"><code><mavenOpts></code></a></td> +<td><a href="#mavenOpts"><code><mavenOpts></code></a></td> <td><code>String</code></td> <td><code>1.2</code></td> <td>The <code>MAVEN_OPTS</code> environment variable to use when invoking Maven. This value can be overridden for individual integration tests by using <a href="#invokerPropertiesFile"><code>invokerPropertiesFile</code></a>. <br /> Since the version <b>3.7.0</b> using an alternate syntax for mavenOpts, <code>@{...}</code> allows late replacement of properties when the plugin is executed, so properties that have been modified by other plugins will be picked up correctly.<br /><strong>User Property</strong>: <code>invoker.mavenOpts</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#mergeUserSettings"><code><mergeUserSettings></code></a></td> +<td><a href="#mergeUserSettings"><code><mergeUserSettings></code></a></td> <td><code>boolean</code></td> <td><code>1.6</code></td> <td>If enable and if you have a settings file configured for the execution, it will be merged with your user settings.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.mergeUserSettings</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#noLog"><code><noLog></code></a></td> +<td><a href="#noLog"><code><noLog></code></a></td> <td><code>boolean</code></td> <td><code>1.0</code></td> <td>Suppress logging to the <code>build.log</code> file.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.noLog</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#parallelThreads"><code><parallelThreads></code></a></td> +<td><a href="#parallelThreads"><code><parallelThreads></code></a></td> <td><code>String</code></td> <td><code>1.6</code></td> <td><p>Number of threads for running tests in parallel. This will be the number of maven forked process in parallel. When terminated with "C", the number part is multiplied by the number of processors (cores) available to the Java virtual machine. Floating point value are only accepted together with "C".</p> <p>Example values: "1.5C", "4"</p><br /><strong>Default</strong>: <code>1</code><br /><strong>User Property</strong>: <code>invoker.parallelThreads</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#pom"><code><pom></code></a></td> +<td><a href="#pom"><code><pom></code></a></td> <td><code>File</code></td> <td><code>1.0</code></td> <td>A single POM to build, skipping any scanning parameters and behavior.<br /><strong>User Property</strong>: <code>invoker.pom</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#pomExcludes"><code><pomExcludes></code></a></td> +<td><a href="#pomExcludes"><code><pomExcludes></code></a></td> <td><code>List<String></code></td> <td><code>1.0</code></td> <td>Exclude patterns for searching the integration test directory. This parameter is meant to be set from the POM. By default, no POM files are excluded. For the convenience of using an include pattern like <code>*</code>, the custom settings file specified by the parameter <a href="#settingsFile"><code>settingsFile</code></a> will always be excluded automatically.</td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#pomIncludes"><code><pomIncludes></code></a></td> +<td><a href="#pomIncludes"><code><pomIncludes></code></a></td> <td><code>List<String></code></td> <td><code>1.0</code></td> <td>Include patterns for searching the integration test directory for projects. This parameter is meant to be set from the POM. If this parameter is not set, the plugin will search for all <code>pom.xml</code> files one directory below <a href="#projectsDirectory"><code>projectsDirectory</code></a> (i.e. <code>*/pom.xml</code>). @@ -417,209 +417,209 @@ invoker.updateSnapshots = true <br /> Starting with version 1.3, mere directories can also be matched by these patterns. For example, the include pattern <code>*</code> will run Maven builds on all immediate sub directories of <a href="#projectsDirectory"><code>projectsDirectory</code></a>, regardless if they contain a <code>pom.xml</code>. This allows to perform builds that need/should not depend on the existence of a POM.</td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#postBuildHookScript"><code><postBuildHookScript></code></a></td> +<td><a href="#postBuildHookScript"><code><postBuildHookScript></code></a></td> <td><code>String</code></td> <td><code>1.0</code></td> <td>Relative path of a cleanup/verification hook script to run after executing the build. This script may be written with either BeanShell or Groovy (since 1.3). If the file extension is omitted (e.g. <code>verify</code>), the plugin searches for the file by trying out the well-known extensions <code>.bsh</code> and <code>.groovy</code>. If this script exists for a particular project but returns any non-null value different from <code>true</code> or throws an exception, the corresponding build is flagged as a failure.<br /><strong>Default</strong>: <code>postbuild</code><br /><strong>User Property</strong>: <code>invoker.postBuildHookScript</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#preBuildHookScript"><code><preBuildHookScript></code></a></td> +<td><a href="#preBuildHookScript"><code><preBuildHookScript></code></a></td> <td><code>String</code></td> <td><code>1.0</code></td> <td>Relative path of a pre-build hook script to run prior to executing the build. This script may be written with either BeanShell or Groovy (since 1.3). If the file extension is omitted (e.g. <code>prebuild</code>), the plugin searches for the file by trying out the well-known extensions <code>.bsh</code> and <code>.groovy</code>. If this script exists for a particular project but returns any non-null value different from <code>true</code> or throws an exception, the corresponding build is flagged as a failure. In this case, neither Maven nor the post-build hook script will be invoked.<br /><strong>Default</strong>: <code>prebuild</code><br /><strong>User Property</strong>: <code>invoker.preBuildHookScript</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#profiles"><code><profiles></code></a></td> +<td><a href="#profiles"><code><profiles></code></a></td> <td><code>List<String></code></td> <td><code>1.1</code></td> <td>List of profile identifiers to explicitly trigger in the build.</td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#projectsDirectory"><code><projectsDirectory></code></a></td> +<td><a href="#projectsDirectory"><code><projectsDirectory></code></a></td> <td><code>File</code></td> <td><code>1.0</code></td> <td>Directory to search for integration tests.<br /><strong>Default</strong>: <code>${basedir}/src/it/</code><br /><strong>User Property</strong>: <code>invoker.projectsDirectory</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#properties"><code><properties></code></a></td> +<td><a href="#properties"><code><properties></code></a></td> <td><code>Map<String,String></code></td> <td><code>1.1</code></td> <td>Common set of properties to pass in on each project's command line, via -D parameters.</td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#quiet"><code><quiet></code></a></td> +<td><a href="#quiet"><code><quiet></code></a></td> <td><code>boolean</code></td> <td><code>3.3.0</code></td> <td>Whether to execute Maven in quiet mode.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.quiet</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#reportsDirectory"><code><reportsDirectory></code></a></td> +<td><a href="#reportsDirectory"><code><reportsDirectory></code></a></td> <td><code>File</code></td> <td><code>1.4</code></td> <td>Base directory where all build reports are written to. Every execution of an integration test will produce an XML file which contains the information about success or failure of that particular build job. The format of the resulting XML file is documented in the given <a href="./build-job.html">build-job</a> reference.<br /><strong>Default</strong>: <code>${project.build.directory}/invoker-reports</code><br /><strong>User Property</strong>: <code>invoker.reportsDirectory</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#scriptVariables"><code><scriptVariables></code></a></td> +<td><a href="#scriptVariables"><code><scriptVariables></code></a></td> <td><code>Map<String,String></code></td> <td><code>1.9</code></td> <td>Additional variables for use in the hook scripts.</td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#selectorScript"><code><selectorScript></code></a></td> +<td><a href="#selectorScript"><code><selectorScript></code></a></td> <td><code>String</code></td> <td><code>1.5</code></td> <td>Relative path of a selector script to run prior in order to decide if the build should be executed. This script may be written with either BeanShell or Groovy. If the file extension is omitted (e.g. <code>selector</code>), the plugin searches for the file by trying out the well-known extensions <code>.bsh</code> and <code>.groovy</code>. If this script exists for a particular project but returns any non-null value different from <code>true</code>, the corresponding build is flagged as skipped. In this case, none of the pre-build hook script, Maven nor the post-build hook script will be invoked. If this script throws an exception, the corresponding build is flagged as in error, and none of the pre-build hook script, Maven not the post-build hook script will be invoked.<br /><strong>Default</strong>: <code>selector</code><br /><strong>User Property</strong>: <code>invoker.selectorScript</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#settingsFile"><code><settingsFile></code></a></td> +<td><a href="#settingsFile"><code><settingsFile></code></a></td> <td><code>File</code></td> <td><code>1.2</code></td> <td>Path to an alternate <code>settings.xml</code> to use for Maven invocation with all ITs. Note that the <code><localRepository></code> element of this settings file is always ignored, i.e. the path given by the parameter <a href="#localRepositoryPath"><code>localRepositoryPath</code></a> is dominant.<br /><strong>User Property</strong>: <code>invoker.settingsFile</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#setupIncludes"><code><setupIncludes></code></a></td> +<td><a href="#setupIncludes"><code><setupIncludes></code></a></td> <td><code>List<String></code></td> <td><code>1.3</code></td> <td>Include patterns for searching the projects directory for projects that need to be run before the other projects. This parameter allows to declare projects that perform setup tasks like installing utility artifacts into the local repository. Projects matched by these patterns are implicitly excluded from the scan for ordinary projects. Also, the exclusions defined by the parameter <a href="#pomExcludes"><code>pomExcludes</code></a> apply to the setup projects, too. Default value is: <code>setup*/pom.xml</code>.</td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#showErrors"><code><showErrors></code></a></td> +<td><a href="#showErrors"><code><showErrors></code></a></td> <td><code>boolean</code></td> <td><code>1.0</code></td> <td>Whether to show errors in the build output.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.showErrors</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#showVersion"><code><showVersion></code></a></td> +<td><a href="#showVersion"><code><showVersion></code></a></td> <td><code>boolean</code></td> <td><code>1.4</code></td> <td>flag to enable show mvn version used for running its (cli option : -V,--show-version )<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.showVersion</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#skipInvocation"><code><skipInvocation></code></a></td> +<td><a href="#skipInvocation"><code><skipInvocation></code></a></td> <td><code>boolean</code></td> <td><code>1.1</code></td> <td>Flag used to suppress certain invocations. This is useful in tailoring the build using profiles.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.skip</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#streamLogs"><code><streamLogs></code></a></td> +<td><a href="#streamLogs"><code><streamLogs></code></a></td> <td><code>boolean</code></td> <td><code>1.0</code></td> <td>Flag used to determine whether the build logs should be output to the normal mojo log.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.streamLogs</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#streamLogsOnFailures"><code><streamLogsOnFailures></code></a></td> +<td><a href="#streamLogsOnFailures"><code><streamLogsOnFailures></code></a></td> <td><code>boolean</code></td> <td><code>3.2.2</code></td> <td>Set to <code>true</code> to output build.log to mojo log in case of failed jobs.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.streamLogsOnFailures</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#suppressSummaries"><code><suppressSummaries></code></a></td> +<td><a href="#suppressSummaries"><code><suppressSummaries></code></a></td> <td><code>boolean</code></td> <td><code>1.0</code></td> <td>Flag used to suppress the summary output notifying of successes and failures. If set to <code>true</code>, the only indication of the build's success or failure will be the effect it has on the main build (if it fails, the main build should fail as well). If <a href="#streamLogs"><code>streamLogs</code></a> is enabled, the sub-build summary will also provide an indication.<br /><strong>Default</strong>: <code>false</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#testPropertiesFile"><code><testPropertiesFile></code></a></td> +<td><a href="#testPropertiesFile"><code><testPropertiesFile></code></a></td> <td><code>String</code></td> <td><code>1.0</code></td> <td>Location of a properties file that defines CLI properties for the test.<br /><strong>Default</strong>: <code>test.properties</code><br /><strong>User Property</strong>: <code>invoker.testPropertiesFile</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#timeoutInSeconds"><code><timeoutInSeconds></code></a></td> +<td><a href="#timeoutInSeconds"><code><timeoutInSeconds></code></a></td> <td><code>int</code></td> <td><code>3.0.2</code></td> <td>No description.<br /><strong>Default</strong>: <code>0</code><br /><strong>User Property</strong>: <code>invoker.timeoutInSeconds</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#updateOnly"><code><updateOnly></code></a></td> +<td><a href="#updateOnly"><code><updateOnly></code></a></td> <td><code>boolean</code></td> <td><code>3.2.2</code></td> <td>Only invoke maven projects if their sources have been modified since they were last built. Only works in conjunction with <code>cloneProjectsTo</code>.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.updateOnly</code></td></tr> <tr class="b"> -<td style="text-align: left;"><a href="#updateSnapshots"><code><updateSnapshots></code></a></td> +<td><a href="#updateSnapshots"><code><updateSnapshots></code></a></td> <td><code>boolean</code></td> <td><code>3.4.0</code></td> <td>Force a check for missing releases and updated snapshots on remote repositories. This is passed to the invoked maven projects (it is the same as if you were to use the -U, --update-snapshots flag on the command line).<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.updateSnapshots</code></td></tr> <tr class="a"> -<td style="text-align: left;"><a href="#writeJunitReport"><code><writeJunitReport></code></a></td> +<td><a href="#writeJunitReport"><code><writeJunitReport></code></a></td> <td><code>boolean</code></td> <td><code>3.1.2</code></td> -<td>Write test result in junit format.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.writeJunitReport</code></td></tr></table></section><section> -<h2>Parameter Details</h2><a id="Parameter_Details"></a><a id="addTestClassPath"></a><section> -<h3><addTestClassPath></h3><a id="a.3CaddTestClassPath.3E"></a> +<td>Write test result in junit format.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>invoker.writeJunitReport</code></td></tr></table></section><section><a id="Parameter_Details"></a> +<h2>Parameter Details</h2><a id="addTestClassPath"></a><section><a id="a.3CaddTestClassPath.3E"></a> +<h3><addTestClassPath></h3> <div>A flag whether the test class path of the project under test should be included in the class path of the pre-/post-build scripts. If set to <code>false</code>, the class path of script interpreter consists only of the <a href="dependencies.html">runtime dependencies</a> of the Maven Invoker Plugin. If set the <code>true</code>, the project's test class path will be prepended to the interpreter class path. Among others, this feature allows the scripts to access utility classes from the test sources of your project.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.2</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.addTestClassPath</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="cloneAllFiles"></a><section> -<h3><cloneAllFiles></h3><a id="a.3CcloneAllFiles.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="cloneAllFiles"></a><section><a id="a.3CcloneAllFiles.3E"></a> +<h3><cloneAllFiles></h3> <div>Some files are normally excluded when copying the IT projects from the directory specified by the parameter projectsDirectory to the directory given by cloneProjectsTo (e.g. <code>.svn</code>, <code>CVS</code>, <code>*~</code>, etc: see <a href="https://codehaus-plexus.github.io/plexus-utils/apidocs/org/codehaus/plexus/util/AbstractScanner.html#DEFAULTEXCLUDES";> reference</a> for full list). Setting this parameter to <code>true</code> will cause all files to be copied to the <code>cloneProjectsTo</code> directory.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.2</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="cloneClean"></a><section> -<h3><cloneClean></h3><a id="a.3CcloneClean.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="cloneClean"></a><section><a id="a.3CcloneClean.3E"></a> +<h3><cloneClean></h3> <div>Ensure the <a href="#cloneProjectsTo"><code>cloneProjectsTo</code></a> directory is not polluted with files from earlier invoker runs.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.6</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>Default</strong>: <code>true</code></li></ul><hr /></section><a id="cloneProjectsTo"></a><section> -<h3><cloneProjectsTo></h3><a id="a.3CcloneProjectsTo.3E"></a> -<div>Directory to which projects should be cloned prior to execution. If set to <code>null</code>, 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.)</div> +<li><strong>Default</strong>: <code>true</code></li></ul><hr /></section><a id="cloneProjectsTo"></a><section><a id="a.3CcloneProjectsTo.3E"></a> +<h3><cloneProjectsTo></h3> +<div>Directory to which projects should be cloned prior to execution. If set to <code>null</code>, 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.) Note: cloning needs to be enabled for properties filtering to work.</div> <ul> <li><strong>Type</strong>: <code>java.io.File</code></li> <li><strong>Since</strong>: <code>1.1</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>User Property</strong>: <code>invoker.cloneProjectsTo</code></li></ul><hr /></section><a id="collectedProjects"></a><section> -<h3><collectedProjects></h3><a id="a.3CcollectedProjects.3E"></a> +<li><strong>User Property</strong>: <code>invoker.cloneProjectsTo</code></li></ul><hr /></section><a id="collectedProjects"></a><section><a id="a.3CcollectedProjects.3E"></a> +<h3><collectedProjects></h3> <div>Projects that are cloned undergo some filtering. In order to grab all projects and make sure they are all filtered, projects are read and parsed. In some cases, this may not be a desired behavior (especially when some pom.xml cannot be parsed by Maven directly). In such cases, the exact list of projects can be set using this field, avoiding the parsing of all pom.xml files found.</div> <ul> <li><strong>Type</strong>: <code>java.util.List<java.lang.String></code></li> <li><strong>Since</strong>: <code>3.9.0</code></li> -<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="debug"></a><section> -<h3><debug></h3><a id="a.3Cdebug.3E"></a> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="debug"></a><section><a id="a.3Cdebug.3E"></a> +<h3><debug></h3> <div>Whether to show debug statements in the build output.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.0</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.debug</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="disableReports"></a><section> -<h3><disableReports></h3><a id="a.3CdisableReports.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="disableReports"></a><section><a id="a.3CdisableReports.3E"></a> +<h3><disableReports></h3> <div>A flag to disable the generation of build reports.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.4</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.disableReports</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="encoding"></a><section> -<h3><encoding></h3><a id="a.3Cencoding.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="encoding"></a><section><a id="a.3Cencoding.3E"></a> +<h3><encoding></h3> <div>The file encoding for the pre-/post-build scripts and the list files for goals and profiles.</div> <ul> <li><strong>Type</strong>: <code>java.lang.String</code></li> <li><strong>Since</strong>: <code>1.2</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>encoding</code></li> -<li><strong>Default</strong>: <code>${project.build.sourceEncoding}</code></li></ul><hr /></section><a id="environmentVariables"></a><section> -<h3><environmentVariables></h3><a id="a.3CenvironmentVariables.3E"></a> +<li><strong>Default</strong>: <code>${project.build.sourceEncoding}</code></li></ul><hr /></section><a id="environmentVariables"></a><section><a id="a.3CenvironmentVariables.3E"></a> +<h3><environmentVariables></h3> <div>Additional environment variables to set on the command line.</div> <ul> <li><strong>Type</strong>: <code>java.util.Map<java.lang.String, java.lang.String></code></li> <li><strong>Since</strong>: <code>1.8</code></li> -<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="failIfNoProjects"></a><section> -<h3><failIfNoProjects></h3><a id="a.3CfailIfNoProjects.3E"></a> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="failIfNoProjects"></a><section><a id="a.3CfailIfNoProjects.3E"></a> +<h3><failIfNoProjects></h3> <div>Set this to <code>true</code> to cause a failure if there are no projects to invoke.</div> <ul> <li><strong>Type</strong>: <code>java.lang.Boolean</code></li> <li><strong>Since</strong>: <code>1.9</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>User Property</strong>: <code>invoker.failIfNoProjects</code></li></ul><hr /></section><a id="filterProperties"></a><section> -<h3><filterProperties></h3><a id="a.3CfilterProperties.3E"></a> +<li><strong>User Property</strong>: <code>invoker.failIfNoProjects</code></li></ul><hr /></section><a id="filterProperties"></a><section><a id="a.3CfilterProperties.3E"></a> +<h3><filterProperties></h3> <div>A list of additional properties which will be used to filter tokens in POMs and goal files.</div> <ul> <li><strong>Type</strong>: <code>java.util.Map<java.lang.String, java.lang.String></code></li> <li><strong>Since</strong>: <code>1.3</code></li> -<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="goals"></a><section> -<h3><goals></h3><a id="a.3Cgoals.3E"></a> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="goals"></a><section><a id="a.3Cgoals.3E"></a> +<h3><goals></h3> <div>The list of goals to execute on each project. Default value is: <code>package</code>.</div> <ul> <li><strong>Type</strong>: <code>java.util.List<java.lang.String></code></li> <li><strong>Since</strong>: <code>1.0</code></li> -<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="ignoreFailures"></a><section> -<h3><ignoreFailures></h3><a id="a.3CignoreFailures.3E"></a> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="ignoreFailures"></a><section><a id="a.3CignoreFailures.3E"></a> +<h3><ignoreFailures></h3> <div>A flag controlling whether failures of the sub builds should fail the main build, too. If set to <code>true</code>, the main build will proceed even if one or more sub builds failed.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.3</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>maven.test.failure.ignore</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="invokerPropertiesFile"></a><section> -<h3><invokerPropertiesFile></h3><a id="a.3CinvokerPropertiesFile.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="invokerPropertiesFile"></a><section><a id="a.3CinvokerPropertiesFile.3E"></a> +<h3><invokerPropertiesFile></h3> <div>The name of an optional project-specific file that contains properties used to specify settings for an individual Maven invocation. Any property present in the file will override the corresponding setting from the plugin configuration. The values of the properties are filtered and may use expressions like <code>${project.version}</code> to reference project properties or values from the parameter <a href="#filterProperties"><code>filterProperties</code></a>. <p></p> <p>As of 3.2.0 it is possible to put this folder in any of the ancestor folders, where properties will be inherited. This way you can provide a single properties file for a group of projects</p> The snippet below describes the supported properties: @@ -752,58 +752,58 @@ invoker.updateSnapshots = true <li><strong>Since</strong>: <code>1.2</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.invokerPropertiesFile</code></li> -<li><strong>Default</strong>: <code>invoker.properties</code></li></ul><hr /></section><a id="invokerTest"></a><section> -<h3><invokerTest></h3><a id="a.3CinvokerTest.3E"></a> +<li><strong>Default</strong>: <code>invoker.properties</code></li></ul><hr /></section><a id="invokerTest"></a><section><a id="a.3CinvokerTest.3E"></a> +<h3><invokerTest></h3> <div>A comma separated list of projectname patterns to run. Specify this parameter to run individual tests by file name, overriding the <a href="#setupIncludes"><code>setupIncludes</code></a>, <a href="#pomIncludes"><code>pomIncludes</code></a> and <a href="#pomExcludes"><code>pomExcludes</code></a> parameters. Each pattern you specify here will be used to create an include/exclude pattern formatted like <code>${projectsDirectory}/<i>pattern</i></code>. To exclude a test, prefix the pattern with a '<code>!</code>'. So you can just type <nobr><code>-Dinvoker.test=SimpleTest,Comp*Test,!Compare*</code></nobr> to run builds in <code>${projectsDirectory}/SimpleTest</code> and <code>${projectsDirectory}/ComplexTest</code>, but not <code>${projectsDirectory}/CompareTest</code></div> <ul> <li><strong>Type</strong>: <code>java.lang.String</code></li> <li><strong>Since</strong>: <code>1.1 (exclusion since 1.8)</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>User Property</strong>: <code>invoker.test</code></li></ul><hr /></section><a id="javaHome"></a><section> -<h3><javaHome></h3><a id="a.3CjavaHome.3E"></a> +<li><strong>User Property</strong>: <code>invoker.test</code></li></ul><hr /></section><a id="javaHome"></a><section><a id="a.3CjavaHome.3E"></a> +<h3><javaHome></h3> <div>The <code>JAVA_HOME</code> environment variable to use for forked Maven invocations. Defaults to the current Java home directory.</div> <ul> <li><strong>Type</strong>: <code>java.io.File</code></li> <li><strong>Since</strong>: <code>1.3</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>User Property</strong>: <code>invoker.javaHome</code></li></ul><hr /></section><a id="junitPackageName"></a><section> -<h3><junitPackageName></h3><a id="a.3CjunitPackageName.3E"></a> +<li><strong>User Property</strong>: <code>invoker.javaHome</code></li></ul><hr /></section><a id="junitPackageName"></a><section><a id="a.3CjunitPackageName.3E"></a> +<h3><junitPackageName></h3> <div>The package name use in junit report</div> <ul> <li><strong>Type</strong>: <code>java.lang.String</code></li> <li><strong>Since</strong>: <code>3.1.2</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.junitPackageName</code></li> -<li><strong>Default</strong>: <code>maven.invoker.it</code></li></ul><hr /></section><a id="localRepositoryPath"></a><section> -<h3><localRepositoryPath></h3><a id="a.3ClocalRepositoryPath.3E"></a> +<li><strong>Default</strong>: <code>maven.invoker.it</code></li></ul><hr /></section><a id="localRepositoryPath"></a><section><a id="a.3ClocalRepositoryPath.3E"></a> +<h3><localRepositoryPath></h3> <div>The local repository for caching artifacts. It is strongly recommended to specify a path to an isolated repository like <code>${project.build.directory}/it-repo</code>. Otherwise, your ordinary local repository will be used, potentially soiling it with broken artifacts.</div> <ul> <li><strong>Type</strong>: <code>java.io.File</code></li> <li><strong>Since</strong>: <code>1.0</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.localRepositoryPath</code></li> -<li><strong>Default</strong>: <code>${settings.localRepository}</code></li></ul><hr /></section><a id="logDirectory"></a><section> -<h3><logDirectory></h3><a id="a.3ClogDirectory.3E"></a> +<li><strong>Default</strong>: <code>${settings.localRepository}</code></li></ul><hr /></section><a id="logDirectory"></a><section><a id="a.3ClogDirectory.3E"></a> +<h3><logDirectory></h3> <div>By default a <code>build.log</code> is created in the root of the project. By setting this folder files are written to a different folder, respecting the structure of the projectsDirectory.</div> <ul> <li><strong>Type</strong>: <code>java.io.File</code></li> <li><strong>Since</strong>: <code>3.2.0</code></li> -<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="mavenExecutable"></a><section> -<h3><mavenExecutable></h3><a id="a.3CmavenExecutable.3E"></a> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="mavenExecutable"></a><section><a id="a.3CmavenExecutable.3E"></a> +<h3><mavenExecutable></h3> <div>mavenExecutable can either be a file relative to <code>${maven.home}/bin/</code>, test project workspace or an absolute file.</div> <ul> <li><strong>Type</strong>: <code>java.lang.String</code></li> <li><strong>Since</strong>: <code>1.8</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>User Property</strong>: <code>invoker.mavenExecutable</code></li></ul><hr /></section><a id="mavenHome"></a><section> -<h3><mavenHome></h3><a id="a.3CmavenHome.3E"></a> +<li><strong>User Property</strong>: <code>invoker.mavenExecutable</code></li></ul><hr /></section><a id="mavenHome"></a><section><a id="a.3CmavenHome.3E"></a> +<h3><mavenHome></h3> <div>The home directory of the Maven installation to use for the forked builds. Defaults to the current Maven installation.</div> <ul> <li><strong>Type</strong>: <code>java.io.File</code></li> <li><strong>Since</strong>: <code>1.3</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>User Property</strong>: <code>invoker.mavenHome</code></li></ul><hr /></section><a id="mavenOpts"></a><section> -<h3><mavenOpts></h3><a id="a.3CmavenOpts.3E"></a> +<li><strong>User Property</strong>: <code>invoker.mavenHome</code></li></ul><hr /></section><a id="mavenOpts"></a><section><a id="a.3CmavenOpts.3E"></a> +<h3><mavenOpts></h3> <div>The <code>MAVEN_OPTS</code> environment variable to use when invoking Maven. This value can be overridden for individual integration tests by using <a href="#invokerPropertiesFile"><code>invokerPropertiesFile</code></a>. <br /> Since the version <b>3.7.0</b> using an alternate syntax for mavenOpts, <code>@{...}</code> allows late replacement of properties when the plugin is executed, so properties that have been modified by other plugins will be picked up correctly.</div> @@ -811,24 +811,24 @@ invoker.updateSnapshots = true <li><strong>Type</strong>: <code>java.lang.String</code></li> <li><strong>Since</strong>: <code>1.2</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>User Property</strong>: <code>invoker.mavenOpts</code></li></ul><hr /></section><a id="mergeUserSettings"></a><section> -<h3><mergeUserSettings></h3><a id="a.3CmergeUserSettings.3E"></a> +<li><strong>User Property</strong>: <code>invoker.mavenOpts</code></li></ul><hr /></section><a id="mergeUserSettings"></a><section><a id="a.3CmergeUserSettings.3E"></a> +<h3><mergeUserSettings></h3> <div>If enable and if you have a settings file configured for the execution, it will be merged with your user settings.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.6</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.mergeUserSettings</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="noLog"></a><section> -<h3><noLog></h3><a id="a.3CnoLog.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="noLog"></a><section><a id="a.3CnoLog.3E"></a> +<h3><noLog></h3> <div>Suppress logging to the <code>build.log</code> file.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.0</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.noLog</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="parallelThreads"></a><section> -<h3><parallelThreads></h3><a id="a.3CparallelThreads.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="parallelThreads"></a><section><a id="a.3CparallelThreads.3E"></a> +<h3><parallelThreads></h3> <div><p>Number of threads for running tests in parallel. This will be the number of maven forked process in parallel. When terminated with "C", the number part is multiplied by the number of processors (cores) available to the Java virtual machine. Floating point value are only accepted together with "C".</p> <p>Example values: "1.5C", "4"</p></div> <ul> @@ -836,21 +836,21 @@ invoker.updateSnapshots = true <li><strong>Since</strong>: <code>1.6</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.parallelThreads</code></li> -<li><strong>Default</strong>: <code>1</code></li></ul><hr /></section><a id="pom"></a><section> -<h3><pom></h3><a id="a.3Cpom.3E"></a> +<li><strong>Default</strong>: <code>1</code></li></ul><hr /></section><a id="pom"></a><section><a id="a.3Cpom.3E"></a> +<h3><pom></h3> <div>A single POM to build, skipping any scanning parameters and behavior.</div> <ul> <li><strong>Type</strong>: <code>java.io.File</code></li> <li><strong>Since</strong>: <code>1.0</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>User Property</strong>: <code>invoker.pom</code></li></ul><hr /></section><a id="pomExcludes"></a><section> -<h3><pomExcludes></h3><a id="a.3CpomExcludes.3E"></a> +<li><strong>User Property</strong>: <code>invoker.pom</code></li></ul><hr /></section><a id="pomExcludes"></a><section><a id="a.3CpomExcludes.3E"></a> +<h3><pomExcludes></h3> <div>Exclude patterns for searching the integration test directory. This parameter is meant to be set from the POM. By default, no POM files are excluded. For the convenience of using an include pattern like <code>*</code>, the custom settings file specified by the parameter <a href="#settingsFile"><code>settingsFile</code></a> will always be excluded automatically.</div> <ul> <li><strong>Type</strong>: <code>java.util.List<java.lang.String></code></li> <li><strong>Since</strong>: <code>1.0</code></li> -<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="pomIncludes"></a><section> -<h3><pomIncludes></h3><a id="a.3CpomIncludes.3E"></a> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="pomIncludes"></a><section><a id="a.3CpomIncludes.3E"></a> +<h3><pomIncludes></h3> <div>Include patterns for searching the integration test directory for projects. This parameter is meant to be set from the POM. If this parameter is not set, the plugin will search for all <code>pom.xml</code> files one directory below <a href="#projectsDirectory"><code>projectsDirectory</code></a> (i.e. <code>*/pom.xml</code>). <br /> <br /> @@ -858,166 +858,166 @@ invoker.updateSnapshots = true <ul> <li><strong>Type</strong>: <code>java.util.List<java.lang.String></code></li> <li><strong>Since</strong>: <code>1.0</code></li> -<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="postBuildHookScript"></a><section> -<h3><postBuildHookScript></h3><a id="a.3CpostBuildHookScript.3E"></a> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="postBuildHookScript"></a><section><a id="a.3CpostBuildHookScript.3E"></a> +<h3><postBuildHookScript></h3> <div>Relative path of a cleanup/verification hook script to run after executing the build. This script may be written with either BeanShell or Groovy (since 1.3). If the file extension is omitted (e.g. <code>verify</code>), the plugin searches for the file by trying out the well-known extensions <code>.bsh</code> and <code>.groovy</code>. If this script exists for a particular project but returns any non-null value different from <code>true</code> or throws an exception, the corresponding build is flagged as a failure.</div> <ul> <li><strong>Type</strong>: <code>java.lang.String</code></li> <li><strong>Since</strong>: <code>1.0</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.postBuildHookScript</code></li> -<li><strong>Default</strong>: <code>postbuild</code></li></ul><hr /></section><a id="preBuildHookScript"></a><section> -<h3><preBuildHookScript></h3><a id="a.3CpreBuildHookScript.3E"></a> +<li><strong>Default</strong>: <code>postbuild</code></li></ul><hr /></section><a id="preBuildHookScript"></a><section><a id="a.3CpreBuildHookScript.3E"></a> +<h3><preBuildHookScript></h3> <div>Relative path of a pre-build hook script to run prior to executing the build. This script may be written with either BeanShell or Groovy (since 1.3). If the file extension is omitted (e.g. <code>prebuild</code>), the plugin searches for the file by trying out the well-known extensions <code>.bsh</code> and <code>.groovy</code>. If this script exists for a particular project but returns any non-null value different from <code>true</code> or throws an exception, the corresponding build is flagged as a failure. In this case, neither Maven nor the post-build hook script will be invoked.</div> <ul> <li><strong>Type</strong>: <code>java.lang.String</code></li> <li><strong>Since</strong>: <code>1.0</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.preBuildHookScript</code></li> -<li><strong>Default</strong>: <code>prebuild</code></li></ul><hr /></section><a id="profiles"></a><section> -<h3><profiles></h3><a id="a.3Cprofiles.3E"></a> +<li><strong>Default</strong>: <code>prebuild</code></li></ul><hr /></section><a id="profiles"></a><section><a id="a.3Cprofiles.3E"></a> +<h3><profiles></h3> <div>List of profile identifiers to explicitly trigger in the build.</div> <ul> <li><strong>Type</strong>: <code>java.util.List<java.lang.String></code></li> <li><strong>Since</strong>: <code>1.1</code></li> -<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="projectsDirectory"></a><section> -<h3><projectsDirectory></h3><a id="a.3CprojectsDirectory.3E"></a> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="projectsDirectory"></a><section><a id="a.3CprojectsDirectory.3E"></a> +<h3><projectsDirectory></h3> <div>Directory to search for integration tests.</div> <ul> <li><strong>Type</strong>: <code>java.io.File</code></li> <li><strong>Since</strong>: <code>1.0</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.projectsDirectory</code></li> -<li><strong>Default</strong>: <code>${basedir}/src/it/</code></li></ul><hr /></section><a id="properties"></a><section> -<h3><properties></h3><a id="a.3Cproperties.3E"></a> +<li><strong>Default</strong>: <code>${basedir}/src/it/</code></li></ul><hr /></section><a id="properties"></a><section><a id="a.3Cproperties.3E"></a> +<h3><properties></h3> <div>Common set of properties to pass in on each project's command line, via -D parameters.</div> <ul> <li><strong>Type</strong>: <code>java.util.Map<java.lang.String, java.lang.String></code></li> <li><strong>Since</strong>: <code>1.1</code></li> -<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="quiet"></a><section> -<h3><quiet></h3><a id="a.3Cquiet.3E"></a> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="quiet"></a><section><a id="a.3Cquiet.3E"></a> +<h3><quiet></h3> <div>Whether to execute Maven in quiet mode.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>3.3.0</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.quiet</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="reportsDirectory"></a><section> -<h3><reportsDirectory></h3><a id="a.3CreportsDirectory.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="reportsDirectory"></a><section><a id="a.3CreportsDirectory.3E"></a> +<h3><reportsDirectory></h3> <div>Base directory where all build reports are written to. Every execution of an integration test will produce an XML file which contains the information about success or failure of that particular build job. The format of the resulting XML file is documented in the given <a href="./build-job.html">build-job</a> reference.</div> <ul> <li><strong>Type</strong>: <code>java.io.File</code></li> <li><strong>Since</strong>: <code>1.4</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.reportsDirectory</code></li> -<li><strong>Default</strong>: <code>${project.build.directory}/invoker-reports</code></li></ul><hr /></section><a id="scriptVariables"></a><section> -<h3><scriptVariables></h3><a id="a.3CscriptVariables.3E"></a> +<li><strong>Default</strong>: <code>${project.build.directory}/invoker-reports</code></li></ul><hr /></section><a id="scriptVariables"></a><section><a id="a.3CscriptVariables.3E"></a> +<h3><scriptVariables></h3> <div>Additional variables for use in the hook scripts.</div> <ul> <li><strong>Type</strong>: <code>java.util.Map<java.lang.String, java.lang.String></code></li> <li><strong>Since</strong>: <code>1.9</code></li> -<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="selectorScript"></a><section> -<h3><selectorScript></h3><a id="a.3CselectorScript.3E"></a> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="selectorScript"></a><section><a id="a.3CselectorScript.3E"></a> +<h3><selectorScript></h3> <div>Relative path of a selector script to run prior in order to decide if the build should be executed. This script may be written with either BeanShell or Groovy. If the file extension is omitted (e.g. <code>selector</code>), the plugin searches for the file by trying out the well-known extensions <code>.bsh</code> and <code>.groovy</code>. If this script exists for a particular project but returns any non-null value different from <code>true</code>, the corresponding build is flagged as skipped. In this case, none of the pre-build hook script, Maven nor the post-build hook script will be invoked. If this script throws an exception, the corresponding build is flagged as in error, and none of the pre-build hook script, Maven not the post-build hook script will be invoked.</div> <ul> <li><strong>Type</strong>: <code>java.lang.String</code></li> <li><strong>Since</strong>: <code>1.5</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.selectorScript</code></li> -<li><strong>Default</strong>: <code>selector</code></li></ul><hr /></section><a id="settingsFile"></a><section> -<h3><settingsFile></h3><a id="a.3CsettingsFile.3E"></a> +<li><strong>Default</strong>: <code>selector</code></li></ul><hr /></section><a id="settingsFile"></a><section><a id="a.3CsettingsFile.3E"></a> +<h3><settingsFile></h3> <div>Path to an alternate <code>settings.xml</code> to use for Maven invocation with all ITs. Note that the <code><localRepository></code> element of this settings file is always ignored, i.e. the path given by the parameter <a href="#localRepositoryPath"><code>localRepositoryPath</code></a> is dominant.</div> <ul> <li><strong>Type</strong>: <code>java.io.File</code></li> <li><strong>Since</strong>: <code>1.2</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>User Property</strong>: <code>invoker.settingsFile</code></li></ul><hr /></section><a id="setupIncludes"></a><section> -<h3><setupIncludes></h3><a id="a.3CsetupIncludes.3E"></a> +<li><strong>User Property</strong>: <code>invoker.settingsFile</code></li></ul><hr /></section><a id="setupIncludes"></a><section><a id="a.3CsetupIncludes.3E"></a> +<h3><setupIncludes></h3> <div>Include patterns for searching the projects directory for projects that need to be run before the other projects. This parameter allows to declare projects that perform setup tasks like installing utility artifacts into the local repository. Projects matched by these patterns are implicitly excluded from the scan for ordinary projects. Also, the exclusions defined by the parameter <a href="#pomExcludes"><code>pomExcludes</code></a> apply to the setup projects, too. Default value is: <code>setup*/pom.xml</code>.</div> <ul> <li><strong>Type</strong>: <code>java.util.List<java.lang.String></code></li> <li><strong>Since</strong>: <code>1.3</code></li> -<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="showErrors"></a><section> -<h3><showErrors></h3><a id="a.3CshowErrors.3E"></a> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a id="showErrors"></a><section><a id="a.3CshowErrors.3E"></a> +<h3><showErrors></h3> <div>Whether to show errors in the build output.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.0</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.showErrors</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="showVersion"></a><section> -<h3><showVersion></h3><a id="a.3CshowVersion.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="showVersion"></a><section><a id="a.3CshowVersion.3E"></a> +<h3><showVersion></h3> <div>flag to enable show mvn version used for running its (cli option : -V,--show-version )</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.4</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.showVersion</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="skipInvocation"></a><section> -<h3><skipInvocation></h3><a id="a.3CskipInvocation.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="skipInvocation"></a><section><a id="a.3CskipInvocation.3E"></a> +<h3><skipInvocation></h3> <div>Flag used to suppress certain invocations. This is useful in tailoring the build using profiles.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.1</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.skip</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="streamLogs"></a><section> -<h3><streamLogs></h3><a id="a.3CstreamLogs.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="streamLogs"></a><section><a id="a.3CstreamLogs.3E"></a> +<h3><streamLogs></h3> <div>Flag used to determine whether the build logs should be output to the normal mojo log.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.0</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.streamLogs</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="streamLogsOnFailures"></a><section> -<h3><streamLogsOnFailures></h3><a id="a.3CstreamLogsOnFailures.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="streamLogsOnFailures"></a><section><a id="a.3CstreamLogsOnFailures.3E"></a> +<h3><streamLogsOnFailures></h3> <div>Set to <code>true</code> to output build.log to mojo log in case of failed jobs.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>3.2.2</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.streamLogsOnFailures</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="suppressSummaries"></a><section> -<h3><suppressSummaries></h3><a id="a.3CsuppressSummaries.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="suppressSummaries"></a><section><a id="a.3CsuppressSummaries.3E"></a> +<h3><suppressSummaries></h3> <div>Flag used to suppress the summary output notifying of successes and failures. If set to <code>true</code>, the only indication of the build's success or failure will be the effect it has on the main build (if it fails, the main build should fail as well). If <a href="#streamLogs"><code>streamLogs</code></a> is enabled, the sub-build summary will also provide an indication.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>1.0</code></li> <li><strong>Required</strong>: <code>No</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="testPropertiesFile"></a><section> -<h3><testPropertiesFile></h3><a id="a.3CtestPropertiesFile.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="testPropertiesFile"></a><section><a id="a.3CtestPropertiesFile.3E"></a> +<h3><testPropertiesFile></h3> <div>Location of a properties file that defines CLI properties for the test.</div> <ul> <li><strong>Type</strong>: <code>java.lang.String</code></li> <li><strong>Since</strong>: <code>1.0</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.testPropertiesFile</code></li> -<li><strong>Default</strong>: <code>test.properties</code></li></ul><hr /></section><a id="timeoutInSeconds"></a><section> -<h3><timeoutInSeconds></h3><a id="a.3CtimeoutInSeconds.3E"></a> +<li><strong>Default</strong>: <code>test.properties</code></li></ul><hr /></section><a id="timeoutInSeconds"></a><section><a id="a.3CtimeoutInSeconds.3E"></a> +<h3><timeoutInSeconds></h3> <div>No description.</div> <ul> <li><strong>Type</strong>: <code>int</code></li> <li><strong>Since</strong>: <code>3.0.2</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.timeoutInSeconds</code></li> -<li><strong>Default</strong>: <code>0</code></li></ul><hr /></section><a id="updateOnly"></a><section> -<h3><updateOnly></h3><a id="a.3CupdateOnly.3E"></a> +<li><strong>Default</strong>: <code>0</code></li></ul><hr /></section><a id="updateOnly"></a><section><a id="a.3CupdateOnly.3E"></a> +<h3><updateOnly></h3> <div>Only invoke maven projects if their sources have been modified since they were last built. Only works in conjunction with <code>cloneProjectsTo</code>.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>3.2.2</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.updateOnly</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="updateSnapshots"></a><section> -<h3><updateSnapshots></h3><a id="a.3CupdateSnapshots.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="updateSnapshots"></a><section><a id="a.3CupdateSnapshots.3E"></a> +<h3><updateSnapshots></h3> <div>Force a check for missing releases and updated snapshots on remote repositories. This is passed to the invoked maven projects (it is the same as if you were to use the -U, --update-snapshots flag on the command line).</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> <li><strong>Since</strong>: <code>3.4.0</code></li> <li><strong>Required</strong>: <code>No</code></li> <li><strong>User Property</strong>: <code>invoker.updateSnapshots</code></li> -<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="writeJunitReport"></a><section> -<h3><writeJunitReport></h3><a id="a.3CwriteJunitReport.3E"></a> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a id="writeJunitReport"></a><section><a id="a.3CwriteJunitReport.3E"></a> +<h3><writeJunitReport></h3> <div>Write test result in junit format.</div> <ul> <li><strong>Type</strong>: <code>boolean</code></li> @@ -1031,7 +1031,7 @@ invoker.updateSnapshots = true <footer> <div class="container-fluid"> <div class="row-fluid"> - <p>© 2002â2024 + <p>© 2002â2025 <a href="https://www.apache.org/";>The Apache Software Foundation</a> </p> </div>
Modified: maven/website/components/plugins-archives/maven-invoker-plugin-LATEST/scm.html ============================================================================== --- maven/website/components/plugins-archives/maven-invoker-plugin-LATEST/scm.html (original) +++ maven/website/components/plugins-archives/maven-invoker-plugin-LATEST/scm.html Mon Jun 23 21:49:14 2025 @@ -2,7 +2,7 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 2.0.0 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.6.1:scm at 2024-12-06 + | Generated by Apache Maven Doxia Site Renderer 2.0.0 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.9.0:scm at 2025-06-23 | Rendered using Apache Maven Fluido Skin 2.0.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> @@ -48,8 +48,8 @@ <li><a href="../index.html">Plugins</a><span class="divider">/</span></li> <li><a href="index.html">Apache Maven Invoker Plugin</a><span class="divider">/</span></li> <li class="active">Source Code Management</li> - <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2024-12-06</li> - <li id="projectVersion" class="pull-right">Version: 3.9.0</li> + <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2025-06-23</li> + <li id="projectVersion" class="pull-right">Version: 3.9.1</li> </ul> </div> </header> @@ -59,7 +59,7 @@ <ul class="nav nav-list"> <li class="nav-header">Overview</li> <li><a href="index.html">Introduction</a></li> - <li><a href="plugin-info.html">Goals</a></li> + <li><a href="plugin-info.html">Plugin Documentation</a></li> <li><a href="usage.html">Usage</a></li> <li><a href="groovy-version.html">Groovy version</a></li> <li><a href="faq.html">FAQ</a></li> @@ -140,19 +140,19 @@ </div> </header> <main id="bodyColumn" class="span10"> -<section> -<h1>Overview</h1><a id="Overview"></a> -<p>This project uses <a class="externalLink" href="https://git-scm.com/";>Git</a> to manage its source code. Instructions on Git use can be found at <a class="externalLink" href="https://git-scm.com/documentation";>https://git-scm.com/documentation</a>.</p></section><section> -<h1>Web Browser Access</h1><a id="Web_Browser_Access"></a> +<section><a id="Overview"></a> +<h1>Overview</h1> +<p>This project uses <a class="externalLink" href="https://git-scm.com/";>Git</a> to manage its source code. Instructions on Git use can be found at <a class="externalLink" href="https://git-scm.com/doc";>https://git-scm.com/doc</a>.</p></section><section><a id="Web_Browser_Access"></a> +<h1>Web Browser Access</h1> <p>The following is a link to a browsable version of the source repository:</p> -<pre><a class="externalLink" href="https://github.com/apache/maven-invoker-plugin/tree/maven-invoker-plugin-3.9.0";>https://github.com/apache/maven-invoker-plugin/tree/maven-invoker-plugin-3.9.0</a></pre></section><section> -<h1>Anonymous Access</h1><a id="Anonymous_Access"></a> +<pre><a class="externalLink" href="https://github.com/apache/maven-invoker-plugin/tree/maven-invoker-plugin-3.9.1";>https://github.com/apache/maven-invoker-plugin/tree/maven-invoker-plugin-3.9.1</a></pre></section><section><a id="Anonymous_Access"></a> +<h1>Anonymous Access</h1> <p>The source can be checked out anonymously from Git with this command (See <a class="externalLink" href="https://git-scm.com/docs/git-clone";>https://git-scm.com/docs/git-clone</a>):</p> -<pre>$ git clone --branch maven-invoker-plugin-3.9.0 https://github.com/apache/maven-invoker-plugin.git</pre></section><section> -<h1>Developer Access</h1><a id="Developer_Access"></a> +<pre>$ git clone --branch maven-invoker-plugin-3.9.1 https://github.com/apache/maven-invoker-plugin.git</pre></section><section><a id="Developer_Access"></a> +<h1>Developer Access</h1> <p>Only project developers can access the Git tree via this method (See <a class="externalLink" href="https://git-scm.com/docs/git-clone";>https://git-scm.com/docs/git-clone</a>).</p> -<pre>$ git clone --branch maven-invoker-plugin-3.9.0 https://github.com/apache/maven-invoker-plugin.git</pre></section><section> -<h1>Access from Behind a Firewall</h1><a id="Access_from_Behind_a_Firewall"></a> +<pre>$ git clone --branch maven-invoker-plugin-3.9.1 https://github.com/apache/maven-invoker-plugin.git</pre></section><section><a id="Access_from_Behind_a_Firewall"></a> +<h1>Access from Behind a Firewall</h1> <p>Refer to the documentation of the SCM used for more information about access behind a firewall.</p></section> </main> </div> </div> @@ -160,7 +160,7 @@ <footer> <div class="container-fluid"> <div class="row-fluid"> - <p>© 2002â2024 + <p>© 2002â2025 <a href="https://www.apache.org/";>The Apache Software Foundation</a> </p> </div> Modified: maven/website/components/plugins-archives/maven-invoker-plugin-LATEST/summary.html ============================================================================== --- maven/website/components/plugins-archives/maven-invoker-plugin-LATEST/summary.html (original) +++ maven/website/components/plugins-archives/maven-invoker-plugin-LATEST/summary.html Mon Jun 23 21:49:14 2025 @@ -2,7 +2,7 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 2.0.0 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.6.1:summary at 2024-12-06 + | Generated by Apache Maven Doxia Site Renderer 2.0.0 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.9.0:summary at 2025-06-23 | Rendered using Apache Maven Fluido Skin 2.0.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> @@ -48,8 +48,8 @@ <li><a href="../index.html">Plugins</a><span class="divider">/</span></li> <li><a href="index.html">Apache Maven Invoker Plugin</a><span class="divider">/</span></li> <li class="active">Project Summary</li> - <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2024-12-06</li> - <li id="projectVersion" class="pull-right">Version: 3.9.0</li> + <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2025-06-23</li> + <li id="projectVersion" class="pull-right">Version: 3.9.1</li> </ul> </div> </header> @@ -59,7 +59,7 @@ <ul class="nav nav-list"> <li class="nav-header">Overview</li> <li><a href="index.html">Introduction</a></li> - <li><a href="plugin-info.html">Goals</a></li> + <li><a href="plugin-info.html">Plugin Documentation</a></li> <li><a href="usage.html">Usage</a></li> <li><a href="groovy-version.html">Groovy version</a></li> <li><a href="faq.html">FAQ</a></li> @@ -140,53 +140,53 @@ </div> </header> <main id="bodyColumn" class="span10"> -<section> -<h1>Project Summary</h1><a id="Project_Summary"></a><section> -<h2>Project Information</h2><a id="Project_Information"></a> +<section><a id="Project_Summary"></a> +<h1>Project Summary</h1><section><a id="Project_Information"></a> +<h2>Project Information</h2> <table class="table table-striped"> <tr class="a"> <th>Field</th> <th>Value</th></tr> <tr class="b"> -<td style="text-align: left;">Name</td> +<td>Name</td> <td>Apache Maven Invoker Plugin</td></tr> <tr class="a"> -<td style="text-align: left;">Description</td> +<td>Description</td> <td>The Maven Invoker Plugin is used to run a set of Maven projects. The plugin can determine whether each project execution is successful, and optionally can verify the output generated from a given project execution.</td></tr> <tr class="b"> -<td style="text-align: left;">Homepage</td> -<td><a class="externalLink" href="https://maven.apache.org/plugins/maven-invoker-plugin/";>https://maven.apache.org/plugins/maven-invoker-plugin/</a></td></tr></table></section><section> -<h2>Project Organization</h2><a id="Project_Organization"></a> +<td>Homepage</td> +<td><a class="externalLink" href="https://maven.apache.org/plugins/maven-invoker-plugin/";>https://maven.apache.org/plugins/maven-invoker-plugin/</a></td></tr></table></section><section><a id="Project_Organization"></a> +<h2>Project Organization</h2> <table class="table table-striped"> <tr class="a"> <th>Field</th> <th>Value</th></tr> <tr class="b"> -<td style="text-align: left;">Name</td> +<td>Name</td> <td>The Apache Software Foundation</td></tr> <tr class="a"> -<td style="text-align: left;">URL</td> -<td><a class="externalLink" href="https://www.apache.org/";>https://www.apache.org/</a></td></tr></table></section><section> -<h2>Build Information</h2><a id="Build_Information"></a> +<td>URL</td> +<td><a class="externalLink" href="https://www.apache.org/";>https://www.apache.org/</a></td></tr></table></section><section><a id="Build_Information"></a> +<h2>Build Information</h2> <table class="table table-striped"> <tr class="a"> <th>Field</th> <th>Value</th></tr> <tr class="b"> -<td style="text-align: left;">GroupId</td> +<td>GroupId</td> <td>org.apache.maven.plugins</td></tr> <tr class="a"> -<td style="text-align: left;">ArtifactId</td> +<td>ArtifactId</td> <td>maven-invoker-plugin</td></tr> <tr class="b"> -<td style="text-align: left;">Version</td> -<td>3.9.0</td></tr> +<td>Version</td> +<td>3.9.1</td></tr> <tr class="a"> -<td style="text-align: left;">Type</td> +<td>Type</td> <td>maven-plugin</td></tr> <tr class="b"> -<td style="text-align: left;">Java Version</td> +<td>Java Version</td> <td>8</td></tr></table></section></section> </main> </div> </div> @@ -194,7 +194,7 @@ <footer> <div class="container-fluid"> <div class="row-fluid"> - <p>© 2002â2024 + <p>© 2002â2025 <a href="https://www.apache.org/";>The Apache Software Foundation</a> </p> </div>
