You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by sv...@apache.org on 2020/03/10 19:55:26 UTC
svn commit: r1875052 [3/4] - in /maven/website/content: ./
apache-resource-bundles/ developers/ developers/release/ docs/3.2.1/
docs/3.2.2/ docs/3.3.1/ docs/3.3.9/ docs/3.5.0-alpha-1/ docs/3.5.0-beta-1/
docs/3.5.0/ docs/3.5.3/ docs/3.5.4/ docs/3.6.0/ d...
Modified: maven/website/content/faq-unoffical.html
==============================================================================
--- maven/website/content/faq-unoffical.html (original)
+++ maven/website/content/faq-unoffical.html Tue Mar 10 19:55:25 2020
@@ -186,8 +186,8 @@ under the License.
<p>[Maven doesn’t work, how do I get help?](#Maven doesn’t work, how do I get help?] [How do I get a list of archetypes?](#How do I get a list of archetypes?] [How do I add main class in a generated jar’s manifest?](#How do I add main class in a generated jar’s manifest?] [How do I run a build/package/deploy process without waiting for reports or unit tests, so that I can quickly deploy to an integration box?](#How do I run a build/package/deploy process without waiting for reports or unit tests, so that I can quickly deploy to an integration box?] [Where is the source code? I couldn’t seem to find a link anywhere on the Maven2 site.](#Where is the source code? I couldn’t seem to find a link anywhere on the Maven2 site.] [How do I configure the equivalent of maven.war.src of war plugin in Maven 2.0?](#How do I configure the equivalent of maven.war.src of war plugin in Maven 2.0?] [How do I add my generated sources to the compile path of Mave
n, when using modello?](#How do I add my generated sources to the compile path of Maven, when using modello?] [Where can I get offline documentation for Maven?](#Where can I get offline documentation for Maven?] [What is the purpose of displaying read-only, plug-in fields in user documentation, if they are not configurable in the project descriptor?](#What is the purpose of displaying read-only, plug-in fields in user documentation, if they are not configurable in the project descriptor?] [How can I disable the timestamp appended in my deployed artifact?](#How can I disable the timestamp appended in my deployed artifact?] [How to run a java program from M2?](#How to run a java program from M2?] [Where to find the source code for org.apache.maven.model package?](#Where to find the source code for org.apache.maven.model package?] [How can I reference windows or unix environment variables in my POM?](#How can I reference windows or unix environment variables in my POM?] [Where to get s
un.jdk-tools-jar-1.4.0 on MacOSX?](#Where to get sun.jdk-tools-jar-1.4.0 on MacOSX?] [How can I make the war plugin produces an exploded war instead of .war file?](#How can I make the war plugin produces an exploded war instead of .war file?] [Is there any variable to determine what version of an artifact was deployed after the deploy step runs?](#Is there any variable to determine what version of an artifact was deployed after the deploy step runs?] [How do I get the top line of a table to be “headers” for that column in APT?](#How do I get the top line of a table to be “headers” for that column in APT?] [What is the suggested way to download a remote file?](#What is the suggested way to download a remote file?] [How do I install the package generated by the assembly plugin to be installed in the local repository?](#How do I install the package generated by the assembly plugin to be installed in the local repository?] [Is it possible to use HashMap as co
nfigurable parameter in a plugin? How do I configure that in pom.xml?](#Is it possible to use HashMap as configurable parameter in a plugin? How do I configure that in pom.xml?] [Which plugins have StarTeam (SCM) support? How do they differ?](#Which plugins have StarTeam (SCM) support? How do they differ?] [How should I point a path for maven 2 to use a certain version of JDK when I have different versions of JDK installed on my PC and my JAVA_HOME already set?](#How should I point a path for maven 2 to use a certain version of JDK when I have different versions of JDK installed on my PC and my JAVA_HOME already set?] [Why does release prepare goal requires the project to be released be a snapshot? Is it possible to do a release prepare from a parent project? What about from a sub-project?](#Why does release prepare goal requires the project to be released be a snapshot? Is it possible to do a release prepare from a parent project? What about from a sub-project?] [How can I create a
n archetype with resources mapped to the class files directory?](#How can I create an archetype with resources mapped to the class files directory?] [What does (f) and (s) debug output mean?](#What does (f) and (s) debug output mean?] [How to resolve problems with jtaxxx.jar?](#How to resolve problems with jtaxxx.jar?] [How to make Continuum work in service mode when an Error 1067 is reported?](#How to make Continuum work in service mode when an Error 1067 is reported?] [Using xdoclet, how come “” does not work?](#Using xdoclet, how come “” does not work?] [I don’t have a domain name and I don’t want use my employer’s domain name. What should I name my plugin package?](#I don’t have a domain name and I don’t want use my employer’s domain name. What should I name my plugin package?] [pom.xml or settings.xml? What is the best practice configuration usage for these files?](#pom.xml or settings.xml? What is the best p
ractice configuration usage for these files?] [What is reactorProjects? executedProject?](#What is reactorProjects? executedProject?] [What is a Snapshot?](#What is a Snapshot?] [Whenever a file is modified in a maven project how is the SNAPSHOT jar updated in the remote repository?](#Whenever a file is modified in a maven project how is the SNAPSHOT jar updated in the remote repository?] [Does maven support automated build and test from non-Java applications?](#Does maven support automated build and test from non-Java applications?] [What would be the appropriate way to enable inheritance of classes in the test hierarchy across modules during the test-compile phase of a multi-pom project?](#What would be the appropriate way to enable inheritance of classes in the test hierarchy across modules during the test-compile phase of a multi-pom project?] [Is Julia Antonova/Tumlare out of the office?](#Is Julia Antonova/Tumlare out of the office?] [How to encrypt a secure password that incl
udes an Ampersand](#How to encrypt a secure password that includes an Ampersand]</p>
<h1>Answered Questions</h1></section><section>
<h3><a name="How_do_I_merge_a_list_of_configuration_items_in_a_parent_POM_with_those_in_a_child_POM.3F"></a>How do I merge a list of configuration items in a parent POM with those in a child POM?</h3>
-<p>Since plugin configurations are handled as XML DOM instances by the core, there is an ever-present struggle between when to merge child elements’ values with one another (when the child’s <source> overrides the parent’s, for example), and when you want to append new child elements to the existing list (as in the example above, or any time you have a list of items to aggregate during inheritance).</p>
-<p>We’ve solved this problem using an attribute, combine.children. You simply specify this attribute, with the value of append at the parent element where such aggregation should occur, and Maven will switch its merge behavior for that element’s children.</p>
+<p>Since plugin configurations are handled as XML DOM instances by the core, there is an ever-present struggle between when to merge child elements’ values with one another (when the child’s <code><source></code> overrides the parent’s, for example), and when you want to append new child elements to the existing list (as in the example above, or any time you have a list of items to aggregate during inheritance).</p>
+<p>We’ve solved this problem using an attribute, <code>combine.children</code>. You simply specify this attribute, with the value of <code>append</code> at the parent element where such aggregation should occur, and Maven will switch its merge behavior for that element’s children.</p>
<p>NOTE: I fixed this behavior in Maven’s trunk; previously, it had been putting the parent POM’s sub-elements AFTER those of the child. This is inconsistent with other inheritance functions, so I’ve reversed the ordering to truly append the child’s elements.</p>
<p>So, to recap:</p>
<p>parent:</p>
@@ -246,7 +246,7 @@ under the License.
</pre></div></div>
</section><section>
<h3><a name="How_do_I_resolve_the_.E2.80.9C.3C_plugin_name_.3E_does_not_exist_or_no_valid_version.E2.80.9D_error.3F"></a>How do I resolve the “< plugin name > does not exist or no valid version” error?</h3>
-<p>This error indicates that Maven is either unable to access the required plug-in from your local repository, or unable to access the official or central Maven plug-in repository.</p>
+<p>This error indicates that Maven is either unable to access the required plug-in from your local repository, or unable to access the official or <code>central</code> Maven plug-in repository.</p>
<p>To resolve this error: - If you are behind a http proxy, please check the Maven2 <a class="externalLink" href="http://maven.apache.org/guides/mini/guide-proxies.html">proxy settings guide</a>. - If you are upgrading Maven from an older version, try running with -U. This will force an update check on all plug-ins.</p>
<p>If the error persists, browse <a class="externalLink" href="http://www.mail-archive.com/users@maven.apache.org/">archived discussions</a>, post to the Maven user list, or log a <a class="externalLink" href="http://jira.codehaus.org/browse/MNG">ticket</a> describing your problem, if you think it is a bug. Tickets may also be issued for feature enhancement requests, and other tasks.</p>
<p>There is a known issue with Maven as of 2.0.4 which is related to metadata files being corrupted during plugin version resolution. For more information, and for a workaround, see <a class="externalLink" href="http://jira.codehaus.org/browse/MNG-2408">MNG-2408</a>.</p>
@@ -314,7 +314,7 @@ under the License.
<p>This command installs the jar in your local repository with the generated generic pom. {{Well, this doesn’t work in Maven 2.0.2. It just gives the message “Cannot execute mojo: install-file. It requires a project with an existing pom.xml, but the build is not using one.” -<a class="externalLink" href="mailto:-kreiger@imcode.com">-kreiger@imcode.com</a>}}</p>
<p><i>Repositories</i></p></section><section>
<h3><a name="How_do_I_install_a_file_in_my_local_repository_along_with_my_customized_POM.3F"></a>How do I install a file in my local repository along with my customized POM?</h3>
-<p>The solution requires at least 2.0.1-SNAPSHOT or above version of Maven 2 and add the -DpomFile=<path-to-pom> parameter just like the sample below.</p>
+<p>The solution requires at least 2.0.1-SNAPSHOT or above version of Maven 2 and add the <code>-DpomFile=<path-to-pom></code> parameter just like the sample below.</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">mvn install:install-file
@@ -390,11 +390,11 @@ under the License.
</pre></div></div>
</section><section>
<h3><a name="Does_the_v4.0.0_POM_include_a_.3C_versions.2F_.3E_element.3F"></a>Does the v4.0.0 POM include a < versions/ > element?</h3>
-<p>The POM does not inlcude a <versions/> element. The POM reflects the current state of a project’s build only, not a historical build log. The POM is not designed to track historical information, as it would be difficult for developers to always add this information manually, i.e., to always remember to add it or to ensure that the correct information is added when multiple branches are involved.</p>
-<p>However, if the SCM tag of the <scm> section of the POM is populated, the repository records build versions, enabling developers to reconstruct the information for each released build.</p>
+<p>The POM does not inlcude a <code><versions/></code> element. The POM reflects the current state of a project’s build only, not a historical build log. The POM is not designed to track historical information, as it would be difficult for developers to always add this information manually, i.e., to always remember to add it or to ensure that the correct information is added when multiple branches are involved.</p>
+<p>However, if the SCM tag of the <code><scm></code> section of the POM is populated, the repository records build versions, enabling developers to reconstruct the information for each released build.</p>
<p><i>POM, General</i></p></section><section>
<h3><a name="How_do_I_create_a_report_that_does_not_require_Doxia.E2.80.99s_Sink_interface.3F"></a>How do I create a report that does not require Doxia’s Sink interface?</h3>
-<p>Make it a report and override the isExternalReport() method to return true.</p>
+<p>Make it a report and override the <code>isExternalReport()</code> method to return true.</p>
<p><i>Sites & Reporting</i></p></section><section>
<h3><a name="How_do_I_prevent_verification_warnings_with_custom_repositories.3F"></a>How do I prevent verification warnings with custom repositories?</h3>
<p>Warnings from custom repositories (usually located within the organization’s network, or even on the same workstation) are triggered when Maven tries to verify the integrity of the files in the repository. This verification is done via the SHA1 or MD5 sum of the file. If these sum files do not exist, then a warning appears.</p>
@@ -440,18 +440,18 @@ rm "$tmpFile"
</pre></div></div>
<p>The script above has been tested on <a class="externalLink" href="http://cygwin.com">Cygwin</a> and is provided “as-is” and with no guarantee. <i>Errors, Repositories</i></p></section><section>
-<h3><a name="What_does_the_.22ERROR:_Cannot_override_read-only_parameter:_.3Cparameter_name.3E_.22_message.2C_when_running_.3Cplugin_name.3E:_mean.3F"></a>What does the "ERROR: Cannot override read-only parameter: <parameter_name> " message, when running <plugin_name>: mean?</h3>
+<h3><a name="What_does_the_.22ERROR:_Cannot_override_read-only_parameter:_.3Cparameter_name.3E_.22_message.2C_when_running_.3Cplugin_name.3E:_mean.3F"></a>What does the "ERROR: Cannot override read-only parameter: <code><parameter_name></code> " message, when running <plugin_name>: mean?</h3>
<p>This means that the parameter being overriden in the pom.xml is read-only. Hence, it is not possible to override this parameter.</p>
<p><i>Errors, POM</i></p></section><section>
<h3><a name="How_do_I_generate_Maven_plug-in_sites.2C_with_pages_that_include_an_overview_of_the_goals_and_parameters_for_each_plug-in.3F"></a>How do I generate Maven plug-in sites, with pages that include an overview of the goals and parameters for each plug-in?</h3>
<p>Include maven-plugin-plugin as a report.</p>
<p><i>Plugin Requests, Sites & Reporting</i></p></section><section>
<h3><a name="Can_I_define_the_antrun_plugin_to_be_executed_on_demand_like_.E2.80.9Cmvn_antrun:run.E2.80.9D.3F"></a>Can I define the antrun plugin to be executed on demand like “mvn antrun:run”?</h3>
-<p>The antrun plugin can be executed on demand only if: - the top level configuration of the plugin contains all the information - a variable is passed from the command line, eg -Dtarget=foo antrun:run - the appropriate target in the script is executed based on the variable</p>
+<p>The antrun plugin can be executed on demand only if: - the top level configuration of the plugin contains all the information - a variable is passed from the command line, eg <code>-Dtarget=foo antrun:run</code> - the appropriate target in the script is executed based on the variable</p>
<p>However, it is recommended that developers write plugins for their goals (Ant support for plugins will be available soon, currently you must write them in java or beanshell).</p>
<p><i>Plugins and Lifecycle, Ant-related</i></p></section><section>
<h3><a name="How_do_I_properly_populate_variables.2C_when_extending_a_mojo_from_another_plugin.3F"></a>How do I properly populate variables, when extending a mojo from another plugin?</h3>
-<p>When creating plugins, the field metadata is read from source files, so it is not available when the original source is not available. While the metadata is available in the plugin in META-INF/maven/plugin.xml, currently, there is no way to incorporate it when building a new plugin.</p>
+<p>When creating plugins, the field metadata is read from source files, so it is not available when the original source is not available. While the metadata is available in the plugin in <code>META-INF/maven/plugin.xml</code>, currently, there is no way to incorporate it when building a new plugin.</p>
<p>It is currently recommended that plug-ins be built using composition, instead of inheritence.</p>
<p><i>Plugin Requests, Design, Patterns & Best Practices</i></p></section><section>
<h3><a name="How_do_I_access_artifacts_if_Ibiblio_is_down.3F"></a>How do I access artifacts if Ibiblio is down?</h3>
@@ -461,7 +461,7 @@ rm "$tmpFile"
<h3><a name="How_do_I_get_a_list_of_archetypes.3F"></a>How do I get a list of archetypes?</h3>
<p>To get a list of archetypes, refer to the following page [<a class="externalLink" href="http://svn.apache.org/viewcvs.cgi/maven/archetype/trunk/maven-archetypes">http://svn.apache.org/viewcvs.cgi/maven/archetype/trunk/maven-archetypes</a>)</p></section><section>
<h3><a name="How_do_I_specify_my_remote_repo_in_Maven_2.0_.28i.e..2C_what_is_the_equivalent_of_.E2.80.98maven.repo.remote.E2.80.99_in_Maven_1.x.29.3F"></a>How do I specify my remote repo in Maven 2.0 (i.e., what is the equivalent of ‘maven.repo.remote’ in Maven 1.x)?</h3>
-<p>To specify a remote repo in Maven 2.0, add the <repositories> element to the POM:</p>
+<p>To specify a remote repo in Maven 2.0, add the <code><repositories></code> element to the POM:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><repositories>
@@ -588,7 +588,7 @@ rm "$tmpFile"
<ul>
-<li>Link the static pages by modifying the <menu> section, create items and map it with the filename of the static pages.</li>
+<li>Link the static pages by modifying the <code><menu></code> section, create items and map it with the filename of the static pages.</li>
</ul>
<div class="source">
@@ -601,14 +601,14 @@ rm "$tmpFile"
<p> <i>Sites & Reporting</i></p></section><section>
<h3><a name="How_do_I_specify_that_all_web_modules_will_inherit_the_group.E2.80.99s_common_files_from_a_parent_web_module.3F"></a>How do I specify that all web modules will inherit the group’s common files from a parent web module?</h3>
-<p>maven-war-plugin 2.0-beta-3 and later supports merging of wars. Just reference the common WAR project from another WAR project as a dependency of <type>war</type> and it will automatically be merged.</p>
+<p>maven-war-plugin 2.0-beta-3 and later supports merging of wars. Just reference the common WAR project from another WAR project as a dependency of <code><type>war</type></code> and it will automatically be merged.</p>
<p>See [<a class="externalLink" href="http://jira.codehaus.org/browse/MWAR-8">http://jira.codehaus.org/browse/MWAR-8</a>)</p>
<p><i>Inheritence and Interpolation</i></p></section><section>
<h3><a name="How_do_I_determine_which_POM_contains_missing_transitive_dependency.3F"></a>How do I determine which POM contains missing transitive dependency?</h3>
-<p>run mvn -X</p>
+<p>run <code>mvn -X</code></p>
<p><i>POM, Dependencies</i></p></section><section>
<h3><a name="Is_there_a_property_file_for_plug-in_configuration_in_Maven_2.0.3F"></a>Is there a property file for plug-in configuration in Maven 2.0?</h3>
-<p>No. Maven 2.x no longer supports plug-in configuration via properties files. Instead, in Maven 2.0 you can configure plug-ins directly from command line using the -D arguement, or from the plug-in’s POM using the <configuration> element.</p>
+<p>No. Maven 2.x no longer supports plug-in configuration via properties files. Instead, in Maven 2.0 you can configure plug-ins directly from command line using the -D arguement, or from the plug-in’s POM using the <code><configuration></code> element.</p>
<p><i>General, POM, Plugins and Lifecycle, Command Line</i></p></section><section>
<h3><a name="How_do_I_determine_the_stale_resources_in_a_Mojo_to_avoid_reprocessing_them.3F"></a>How do I determine the stale resources in a Mojo to avoid reprocessing them?</h3>
<p>This can be done using the following piece of code:</p>
@@ -625,7 +625,7 @@ import org.codehaus.plexus.compiler.util
Set<File> staleFiles = (Set<File>) scanner.getIncludedSources( this.sourceDirectory, this.targetDirectory );
</pre></div></div>
-<p>The second parameter to the StaleSourceScanner is the set of includes, while the third parameter is the set of excludes. You must add a source mapping to the scanner (second line). In this case we’re telling the scanner what is the extension of the result file (.html) for each source file extension (.xml). Finally we get the stale files as a Set<File> calling the getIncludedSources method, passing as parameters the source and target directories (of type File). The Maven API doesn’t support generics, but you may cast it that way if you’re using them. In order to use this API you must include the following dependency in your pom:</p>
+<p>The second parameter to the StaleSourceScanner is the set of includes, while the third parameter is the set of excludes. You must add a source mapping to the scanner (second line). In this case we’re telling the scanner what is the extension of the result file (.html) for each source file extension (.xml). Finally we get the stale files as a <code>Set<File></code> calling the <code>getIncludedSources</code> method, passing as parameters the source and target directories (of type File). The Maven API doesn’t support generics, but you may cast it that way if you’re using them. In order to use this API you must include the following dependency in your pom:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><dependencies>
@@ -676,8 +676,8 @@ import org.codehaus.plexus.compiler.util
<p>While this may seem a counter-intuitive way of configuring a report, it’s important to remember that Maven plugins can have a mix of reports and normal mojos. When a POM has to configure extra dependencies for a plugin, it should do so in the normal plugins section. We will probably try to fix this problem before the next release of the checkstyle plugin.</p>
<p><i>UPDATE:</i> This problem has been fixed in the SVN trunk version of the checkstyle plugin, which should be released very soon. <i>Plugins and Lifecycle, Sites & Reporting, Errors</i></p><section>
<h3><a name="Where_do_I_configure_report_plug-ins.2C_like_javadoc.3F"></a>Where do I configure report plug-ins, like javadoc?</h3>
-<p>Generally, you should configure reporting in the <reporting> (vs. <build>) section of the POM. Configuration there applies to both the site, and when run on the command line, and adding the plugin there adds the report to the generated site.</p>
-<p>Configuration in the build section is only used during the normal lifecycle or the command line invocation (eg javadoc:javadoc).</p>
+<p>Generally, you should configure reporting in the <code><reporting></code> (vs. <code><build></code>) section of the POM. Configuration there applies to both the site, and when run on the command line, and adding the plugin there adds the report to the generated site.</p>
+<p>Configuration in the build section is only used during the normal lifecycle or the command line invocation (eg <code>javadoc:javadoc</code>).</p>
<p>Configuration should go there if you do not want the report on the site, or the configuration differs from what is on the site (eg, some plugins have a fail build option).</p>
<p><i>Sites & Reporting, Plugins and Lifecycle, Command Line</i></p></section><section>
<h3><a name="How_do_I_deploy_my_binary_during_the_deploy_phase.3F"></a>How do I deploy my binary during the deploy phase?</h3>
@@ -700,7 +700,7 @@ import org.codehaus.plexus.compiler.util
</plugin>
</pre></div></div>
-<p>Then run mvn deploy. <i>Deployment</i></p></section><section>
+<p>Then run <code>mvn deploy</code>. <i>Deployment</i></p></section><section>
<h3><a name="How_do_I_add_main_class_in_a_generated_jar.E2.80.99s_manifest.3F"></a>How do I add main class in a generated jar’s manifest?</h3>
<p>Configure the maven-jar-plugin and add your main class.</p>
@@ -719,7 +719,7 @@ import org.codehaus.plexus.compiler.util
</pre></div></div>
</section><section>
<h3><a name="How_do_I_install_artifacts_to_a_remote_repository.3F"></a>How do I install artifacts to a remote repository?</h3>
-<p>You need at least 2.1-SNAPSHOT version of maven-deploy-plugin to make this work, current workaround to use this is to copy the wagon provider jar (ie. wagon-ftp-1.0-alpha-3.jar) in your %M2_HOME%/lib and execute the command:</p>
+<p>You need at least 2.1-SNAPSHOT version of maven-deploy-plugin to make this work, current workaround to use this is to copy the wagon provider jar (ie. wagon-ftp-1.0-alpha-3.jar) in your <code>%M2_HOME%/lib</code> and execute the command:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">mvn deploy:deploy-file
@@ -802,7 +802,7 @@ import org.codehaus.plexus.compiler.util
</build>
</pre></div></div>
-<p>and run mvn install, this will execute the assembly plugin twice with different config.</p></section><section>
+<p>and run <code>mvn install</code>, this will execute the assembly plugin twice with different config.</p></section><section>
<h3><a name="What_is_Maven.E2.80.99s_order_of_inheritance.3F"></a>What is Maven’s order of inheritance?</h3>
<ul>
@@ -821,8 +821,8 @@ import org.codehaus.plexus.compiler.util
<p>You can’t, but you can use the assembly plugin to create a source distribution and a binary distribution for your project</p>
<p>Please refer to these sites for more info [http://maven.apache.org/guides/mini/guide-assemblies.html] [http://maven.apache.org/plugins/maven-assembly-plugin/howto.html]</p>
<p><i>Deployments, Plugins and Lifecycle</i></p></section><section>
-<h3><a name="What_does_the_.E2.80.9CYou_cannot_have_two_plugin_executions_with_the_same_.28or_missing.29_.3Cid.2F.3E_elements.E2.80.9D_message_mean.3F"></a>What does the “You cannot have two plugin executions with the same (or missing) <id/> elements” message mean?</h3>
-<p>It means that you have executed a plugin multiple times with the same <id>. Provide each <execution> with a unique <id> then it would be ok.</p>
+<h3><a name="What_does_the_.E2.80.9CYou_cannot_have_two_plugin_executions_with_the_same_.28or_missing.29_.3Cid.2F.3E_elements.E2.80.9D_message_mean.3F"></a>What does the “You cannot have two plugin executions with the same (or missing) <code><id/></code> elements” message mean?</h3>
+<p>It means that you have executed a plugin multiple times with the same <code><id></code>. Provide each <code><execution></code> with a unique <code><id></code> then it would be ok.</p>
<p><i>Errors, Plugins and Lifecycle</i></p></section><section>
<h3><a name="Can_I_disable_transitive_dependencies.3F"></a>Can I disable transitive dependencies?</h3>
<p>No you can’t, but you may exclude the dependencies you dont want to include in your project.</p>
@@ -851,9 +851,9 @@ import org.codehaus.plexus.compiler.util
<p>Check it out from [http://svn.apache.org/repos/asf/maven/site/trunk] and run mvn site:site</p>
<p><i>General, Sites & Reporting</i></p></section><section>
<h3><a name="How_do_I_skip_unit_tests_when_building_a_project.3F"></a>How do I skip unit tests when building a project?</h3>
-<p>Run the mvn command with -Dmaven.test.skip=true argument.</p>
+<p>Run the mvn command with <code>-Dmaven.test.skip=true</code> argument.</p>
<p>Also see [How do I run a build/package/deploy process without waiting for reports or unit tests, so that I can quickly deploy to an integration box?]</p></section><section>
-<h3><a name="How_do_I_convert_my_.3Creports.3E_from_Maven_1_to_Maven_2.3F"></a>How do I convert my <reports> from Maven 1 to Maven 2?</h3>
+<h3><a name="How_do_I_convert_my_.3Creports.3E_from_Maven_1_to_Maven_2.3F"></a>How do I convert my <code><reports></code> from Maven 1 to Maven 2?</h3>
<p>In m1, we declare reports in the pom like this:</p>
<div class="source">
@@ -866,7 +866,7 @@ import org.codehaus.plexus.compiler.util
</project>
</pre></div></div>
-<p>In m2, the <reports> tag is replaced with <reporting></p>
+<p>In m2, the <code><reports></code> tag is replaced with <code><reporting></code></p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><project>
@@ -894,7 +894,7 @@ import org.codehaus.plexus.compiler.util
<p><i>Sites & Reporting, General</i></p></section><section>
<h3><a name="How_do_I_create_a_command_line_parameter_.28i.e..2C_-Dname.3Dvalue_.29_in_my_mojo.3F"></a>How do I create a command line parameter (i.e., -Dname=value ) in my mojo?</h3>
-<p>In your mojo, put expression=$\{<exp>\} in your parameter field</p>
+<p>In your mojo, put <code>expression=$\{<exp>\}</code> in your parameter field</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">/**
@@ -903,10 +903,10 @@ import org.codehaus.plexus.compiler.util
private String exp;
</pre></div></div>
-<p>You may now able to pass parameter values to the command line. mvn \-Dexpression.name=value install</p>
+<p>You may now able to pass parameter values to the command line. <code>mvn \-Dexpression.name=value install</code></p>
<p><i>Command Line</i></p></section><section>
<h3><a name="What_is_the_purpose_of_displaying_read-only.2C_plug-in_fields_in_user_documentation.2C_if_they_are_not_configurable_in_the_project_descriptor.3F"></a>What is the purpose of displaying read-only, plug-in fields in user documentation, if they are not configurable in the project descriptor?</h3>
-<p>Often, parameters are specified as read-only to indicate that its value should be changed indirectly, rather than in the plugins <configuration/> section. For instance, I may have a plugin that declares a parameter as such:</p>
+<p>Often, parameters are specified as read-only to indicate that its value should be changed indirectly, rather than in the plugins <code><configuration/></code> section. For instance, I may have a plugin that declares a parameter as such:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">/**
@@ -917,7 +917,7 @@ private String exp;
private File buildDir;
</pre></div></div>
-<p>In this case, my plugin wants to output something to the project’s build directory. If this were configured directly on the plugin, it might not be cleaned up when the user issued <i>‘mvn clean’</i>, so instead I mark it as @readonly. This tells the user that she should modify the structure referenced by <i>default-value</i>(i.e. <project><build><directory/> in the POM) instead, which will allow this plugin to be a good citizen in the build process.</p></section><section>
+<p>In this case, my plugin wants to output something to the project’s build directory. If this were configured directly on the plugin, it might not be cleaned up when the user issued <i>‘mvn clean’</i>, so instead I mark it as <code>@readonly</code>. This tells the user that she should modify the structure referenced by <i>default-value</i>(i.e. <code><project><build><directory/></code> in the POM) instead, which will allow this plugin to be a good citizen in the build process.</p></section><section>
<h3><a name="I.E2.80.99ve_just_created_a_maven_plugin._Is_there_a_sample_plugin_integration_test_I_can_use.3F"></a>I’ve just created a maven plugin. Is there a sample plugin integration test I can use?</h3>
<p>Each integration test is a separate project. For a plugin, you may want to create a project that will use your plugin and probably put it inside src/test/projects like maven-antrun-plugin, maven-eclipse-plugin, maven-javadoc-plugin and several others. These plugins can be found here: [https://svn.apache.org/repos/asf/maven/plugins/trunk]</p>
<p><i>Plugins and Lifecycle, Sites & Reporting, Integration tests</i></p></section><section>
@@ -949,7 +949,7 @@ private String exp;
</plugin>
</pre></div></div>
-<p>On the solaris machine In $HOME/.profile MAVEN_OPTS="-Xmx512m -Xms512m -Dfile.encoding=ISO-8859-1 (mx/ms not mandatory for m2 but for m1). LANG=en_US.ISO8859-15 <i>Sites & Reporting, IDEs</i></p></section><section>
+<p>On the solaris machine In <code>$HOME/.profile</code> <code>MAVEN_OPTS="-Xmx512m -Xms512m -Dfile.encoding=ISO-8859-1</code> (mx/ms not mandatory for m2 but for m1). <code>LANG=en_US.ISO8859-15</code> <i>Sites & Reporting, IDEs</i></p></section><section>
<h3><a name="How_do_I_generate_sources_with_the_antrun_plug-in.3F"></a>How do I generate sources with the antrun plug-in?</h3>
<p>For instance to generate sources add the following to your plugins section NOTE: this may only work in the latest plugin version in SVN</p>
@@ -986,10 +986,10 @@ private String exp;
<p><i>Ant-related</i> </p></section><section>
<h3><a name="Where_is_the_plugin-registry.xml.3F"></a>Where is the plugin-registry.xml?</h3>
-<p>From the settings.xml, you may enable it by setting <usePluginRegistry/> to true and the file will be in ~/.m2/plugin-registry.xml</p>
+<p>From the settings.xml, you may enable it by setting <code><usePluginRegistry/></code> to true and the file will be in <code>~/.m2/plugin-registry.xml</code></p>
<p><i>General, Plugins and Lifecycle</i></p></section><section>
<h3><a name="Is_there_a_way_to_specify_a_different_output_directory_without_having_to_edit_the_pom_or_configuration_file_each_time_I_do_a_build.3F"></a>Is there a way to specify a different output directory without having to edit the pom or configuration file each time I do a build?</h3>
-<p>Yes. You can make use of the pom’s <properties> element to accomplish this.</p>
+<p>Yes. You can make use of the pom’s <code><properties></code> element to accomplish this.</p>
<p>To do so, simply add the following fragment to your pom:</p>
<div class="source">
@@ -1055,7 +1055,7 @@ i.e.
</pre></div></div>
<p><i>Repositories</i></p></section><section>
-<h3><a name="I_have_my_web.xml_in_my_customed_directory_layout_for_my_webapp.2C_but_why_am_I_getting_the_error_.E2.80.9CDeployment_descriptor_.3CPath.3E.5CWEB-INF.5Cweb.xml_does_not_exist.E2.80.9D.3F"></a>I have my web.xml in my customed directory layout for my webapp, but why am I getting the error “Deployment descriptor <Path>\WEB-INF\web.xml does not exist”?</h3>
+<h3><a name="I_have_my_web.xml_in_my_customed_directory_layout_for_my_webapp.2C_but_why_am_I_getting_the_error_.E2.80.9CDeployment_descriptor_.3CPath.3E.5CWEB-INF.5Cweb.xml_does_not_exist.E2.80.9D.3F"></a>I have my web.xml in my customed directory layout for my webapp, but why am I getting the error “Deployment descriptor <code><Path>\WEB-INF\web.xml</code> does not exist”?</h3>
<p>You may specify the path of your web.xml in your webapp by configuring maven-war-plugin.</p>
<div class="source">
@@ -1074,7 +1074,7 @@ i.e.
</pre></div></div>
<p><i>Errors, Deployment</i> </p></section><section>
-<h3><a name="Is_it_possible_to_specify_multiple_.3Cmodule.3E.28s.29_in_a_POM_at_a_greater_depth_than_1_level.3F"></a>Is it possible to specify multiple <module>(s) in a POM at a greater depth than 1 level?</h3>
+<h3><a name="Is_it_possible_to_specify_multiple_.3Cmodule.3E.28s.29_in_a_POM_at_a_greater_depth_than_1_level.3F"></a>Is it possible to specify multiple <code><module></code>(s) in a POM at a greater depth than 1 level?</h3>
<p>Yes. This can be done in two ways: 1. add the extra path in the top level POM, or 2. add extra parent poms at different levels, if approriate.</p>
<p>For example, you have the following structure: /A/pom.xml (multi-module POM) /A/B/C/pom.xml /A/B/C/D/pom.xml</p>
<p>And you want the modules at level C and D built when the multi-module POM is built.</p>
@@ -1129,7 +1129,7 @@ e.g. mvn eclipse:help
<p><i>Plugins and Lifecycle, IDEs</i></p></section><section>
<h3><a name="What_does_aggregator_mean_in_mojo.3F"></a>What does aggregator mean in mojo?</h3>
-<p>When a Mojo has a @aggregator expression, it means that It can only build the parent project of your multi-module-project, the one who has the packaging of pom. It can also give you values for the expression ${reactorProjects} where reactorProjects are the MavenProject references to the parent pom modules.</p></section><section>
+<p>When a Mojo has a <code>@aggregator</code> expression, it means that It can only build the parent project of your multi-module-project, the one who has the packaging of pom. It can also give you values for the expression ${reactorProjects} where reactorProjects are the MavenProject references to the parent pom modules.</p></section><section>
<h3><a name="Why_there_are_no_dependency_properties_in_Maven_2.3F"></a>Why there are no dependency properties in Maven 2?</h3>
<p>They were removed because they aren’t reliable in a transitive environment. It implies that the dependency knows something about the environment of the dependee, which is back to front. In most cases, granted, the value for war bundle will be the same for a particular dependency - but that relies on the dependency specifying it.</p>
<p>In the end, we give control to the actual POM doing the building, trying to use sensible defaults that minimise what needs to be specified, and allowing the use of artifact filters in the configuration of plugins.</p></section><section>
@@ -1144,7 +1144,7 @@ e.g. mvn eclipse:help
<p>There are currently 2 alternatives: * For use in a plugin written in Java, Beanshell or other Java-like scripting language, you can construct the Ant tasks <a class="externalLink" href="http://ant.apache.org/manual/antexternal.html">using the instructions given in the Ant documentation</a> * If you have very small amounts of Ant script specific to your project, you can use the <a class="externalLink" href="http://maven.apache.org/plugins/maven-antrun-plugin/index.html">AntRun plugin</a>.</p></section><section>
<h3><a name="Is_it_possible_to_create_my_own_directory_structure.3F"></a>Is it possible to create my own directory structure?</h3>
<p>Absolutely yes!</p>
-<p>By configuring <sourceDirectory>, <resources> and other elements of the <build> section.</p>
+<p>By configuring <code><sourceDirectory></code>, <code><resources></code> and other elements of the <code><build></code> section.</p>
<p>In addition, you may need to change the plugin configuration if you are not using plugin defaults for their files/directories.</p></section><section>
<h3><a name="Where_is_the_source_code.3F_I_couldn.E2.80.99t_seem_to_find_a_link_anywhere_on_the_Maven2_site."></a>Where is the source code? I couldn’t seem to find a link anywhere on the Maven2 site.</h3>
<p>The source code can be found in subversion: [http://svn.apache.org/repos/asf/maven/components/trunk].</p>
@@ -1250,12 +1250,12 @@ e.g. mvn eclipse:help
<h3><a name="Unsupported_Protocol_Error_when_deploying_a_3rd_party_jar._What_should_I_do.3F"></a>Unsupported Protocol Error when deploying a 3rd party jar. What should I do?</h3>
<p>When using deploy-deploy-file goal and encountered this error</p>
<p>“Error deploying artifact: Unsupported Protocol: ‘ftp’: Cannot find wagon which supports the requested protocol: ftp”</p>
-<p>You only have to place the appropriate wagon provider to your %M2_HOME%/lib In this case the provider needed is ftp, so we have to place the wagon-ftp jar to the lib of your m2 installation.</p>
+<p>You only have to place the appropriate wagon provider to your <code>%M2_HOME%/lib</code> In this case the provider needed is ftp, so we have to place the wagon-ftp jar to the lib of your m2 installation.</p>
<p>If the error description is something like</p>
<p>“Error deploying artifact: Unsupported Protocol: ‘ftp’: Cannot find wagon which supports the requested protocol: ftp org/apache/commons/net/ftp/FTP”</p>
<p>Place also the commons-net jar to %M2_HOME%/lib.</p></section><section>
<h3><a name="How_can_I_have_a_child_project_not_inherit_a_goal_.28like_install.29_from_the_parent.3F"></a>How can I have a child project not inherit a goal (like install) from the parent?</h3>
-<p>Use the inherited property. Set it to false in the plugin configuration. So for example, if you want your parent project to be installed but not your child, configure the install plugin like so:</p>
+<p>Use the <code>inherited</code> property. Set it to <code>false</code> in the plugin configuration. So for example, if you want your parent project to be installed but not your child, configure the install plugin like so:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><plugin>
@@ -1267,12 +1267,12 @@ e.g. mvn eclipse:help
</pre></div></div>
</section><section>
<h3><a name="How_can_I_reference_windows_or_unix_environment_variables_in_my_POM.3F"></a>How can I reference windows or unix environment variables in my POM?</h3>
-<p>Starting in maven <i>2.0.1</i>, you can reference windows and unix environment variables inside your pom.xml or settings.xml using an expression of the form: $\{env.VARNAME\} So, if you wanted to reference your home directory environment variable, you might use: $\{env.HOME\}</p></section><section>
+<p>Starting in maven <i>2.0.1</i>, you can reference windows and unix environment variables inside your pom.xml or settings.xml using an expression of the form: <code>$\{env.VARNAME\}</code> So, if you wanted to reference your home directory environment variable, you might use: <code>$\{env.HOME\}</code></p></section><section>
<h3><a name="How_do_I_know_which_phase_a_plug-in_is_associated_with.3F"></a>How do I know which phase a plug-in is associated with?</h3>
<p>Open the plugin’s Mojo class source code and look for @phase. This tells which phase the plugin is associated.</p></section><section>
<h3><a name="Where_to_get_sun.jdk-tools-jar-1.4.0_on_MacOSX.3F"></a>Where to get sun.jdk-tools-jar-1.4.0 on MacOSX?</h3>
<p>There are no tools.jar on a mac. The classes are included in the normal java runtime ( /System/Library/Frameworks/ JavaVM.framework/Classes/classes.jar. Refer to this link [http://lists.apple.com/archives/java-dev/2002/Jun/msg00901.html] )</p>
-<p>You only have to modify the <systemPath> pointing to your classes.jar on MacOSX.</p>
+<p>You only have to modify the <code><systemPath></code> pointing to your classes.jar on MacOSX.</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><dependency>
@@ -1316,7 +1316,7 @@ e.g. mvn eclipse:help
<p>As of now, There is no tool for it. You have to manually delete them in your local repository. However, there is already some discussion about this, Please refer to this links for more info.</p>
<p>[http://jira.codehaus.org/browse/MNG-233] [http://jira.codehaus.org/browse/MRELEASE-68]</p></section><section>
<h3><a name="How_to_make_a_war_artifact_as_a_dependency.3F"></a>How to make a war artifact as a dependency?</h3>
-<p>When specifying a war as dependency, make sure that you have set the <type> to war.</p>
+<p>When specifying a war as dependency, make sure that you have set the <code><type></code> to war.</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><dependency>
@@ -1358,7 +1358,7 @@ e.g. mvn eclipse:help
<h3><a name="How_can_I_make_the_war_plugin_produces_an_exploded_war_instead_of_.war_file.3F"></a>How can I make the war plugin produces an exploded war instead of .war file?</h3>
<p>You may use war:exploded goal for this.</p></section><section>
<h3><a name="Is_there_any_variable_to_determine_what_version_of_an_artifact_was_deployed_after_the_deploy_step_runs.3F"></a>Is there any variable to determine what version of an artifact was deployed after the deploy step runs?</h3>
-<p>Use $project.artifact.resolvedVersion.</p></section><section>
+<p>Use <code>$project.artifact.resolvedVersion</code>.</p></section><section>
<h3><a name="How_do_I_get_the_top_line_of_a_table_to_be_.E2.80.9Cheaders.E2.80.9D_for_that_column_in_APT.3F"></a>How do I get the top line of a table to be “headers” for that column in APT?</h3>
<p>With the snapshot you can do:</p>
@@ -1399,9 +1399,9 @@ Wagon wagon;
</project
</pre></div></div>
-<p>Also, you can have assembly plugin use a different directory by setting the plugin parameter outputDirectory to your desired directory. More info about the assembly plugin can be found here: [http://maven.apache.org/plugins/maven-assembly-plugin/introduction.html]</p></section><section>
+<p>Also, you can have assembly plugin use a different directory by setting the plugin parameter <code>outputDirectory</code> to your desired directory. More info about the assembly plugin can be found here: [http://maven.apache.org/plugins/maven-assembly-plugin/introduction.html]</p></section><section>
<h3><a name="How_do_I_filter_which_classes_should_be_put_inside_the_packaged_jar.3F"></a>How do I filter which classes should be put inside the packaged jar?</h3>
-<p>All compiled classes are always put into the packaged jar. However, you can configure the compiler plugin to exclude compiling some of the java sources using the compiler parameter excludes as follows:</p>
+<p>All compiled classes are always put into the packaged jar. However, you can configure the compiler plugin to exclude compiling some of the java sources using the compiler parameter <code>excludes</code> as follows:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><project>
@@ -1443,7 +1443,7 @@ Wagon wagon;
<h3><a name="Which_plugins_have_StarTeam_.28SCM.29_support.3F_How_do_they_differ.3F"></a>Which plugins have StarTeam (SCM) support? How do they differ?</h3>
<p>maven-scm-plugin and maven-release-plugin support via maven-scm’s API and maven-scm-provider-starteam. Release plugin is used to cut a new release of your project (label, build, assembly, deploy, etc.). SCM plugin, on the other hand, is for scm tasks.</p></section><section>
<h3><a name="Is_there_a_way_to_use_the_deploy_phase_to_perform_some_tasks_without_maven_trying_to_install_the_artifact_to_a_maven_repository.3F"></a>Is there a way to use the deploy phase to perform some tasks without maven trying to install the artifact to a maven repository?</h3>
-<p>If you run ‘mvn deploy’, the ‘maven-deploy-plugin’ kicks in. There’s no flag that tells it not to upload the file. So you’d have to make a new lifecycle mapping/packaging for each <type> of artifact in your project. There’s no way to ‘delete’ mojo’s from the default lifecycle. What you could do is specify the remote repo as [file:///tmp]or something. Usually people want to ‘upload’ a war to the tomcat webapps dir, also known as deploying. That kind of deploying is not something m2 has a phase for.</p>
+<p>If you run ‘mvn deploy’, the ‘maven-deploy-plugin’ kicks in. There’s no flag that tells it not to upload the file. So you’d have to make a new lifecycle mapping/packaging for each <code><type></code> of artifact in your project. There’s no way to ‘delete’ mojo’s from the default lifecycle. What you could do is specify the remote repo as [file:///tmp]or something. Usually people want to ‘upload’ a war to the tomcat webapps dir, also known as deploying. That kind of deploying is not something m2 has a phase for.</p>
<p>What you can do is create a profile in the pom (or super pom), and add a task/mojo to the ‘install’ phase. For instance, you can have the antrun plugin copy the artifact to the tomcat directory (its location specified in settings.xml). The profile is named ‘dev’, so whenever you want to deploy a war, you just type ‘mvn install -Pdev’. Don’t bind to the deploy phase, but to the install or package phase.</p></section><section>
<h3><a name="Repository_precedence"></a>Repository precedence</h3>
<p>The repositories are searched through based in the order they are defined in your pom. The inherited repositories are always searched last. Note: You don’t have to define the central repo (i.e. ibiblio).</p></section><section>
@@ -1466,7 +1466,7 @@ Wagon wagon;
</pre></div></div>
</section><section>
<h3><a name="How_do_I_add_a_description_to_the_welcome_page_of_the_generated_site_when_I_execute_mvn_site.3F"></a>How do I add a description to the welcome page of the generated site when I execute mvn site?</h3>
-<p>Fille up the <description> in the pom.xml as shown below:</p>
+<p>Fille up the <code><description></code> in the pom.xml as shown below:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><project>
@@ -1479,7 +1479,7 @@ Wagon wagon;
<h3><a name="What_does_.28f.29_and_.28s.29_debug_output_mean.3F"></a>What does (f) and (s) debug output mean?</h3>
<p>(f) is for field injection while (s) is for setter injection.</p></section><section>
<h3><a name="Is_there_a_preferred_way_to_communicate_dependencies_in_documentation.3F"></a>Is there a preferred way to communicate dependencies in documentation?</h3>
-<p>Same format used in Maven error reporting: groupId:artifactId:version This should be easy to understand by Maven users.</p></section><section>
+<p>Same format used in Maven error reporting: <code>groupId:artifactId:version</code> This should be easy to understand by Maven users.</p></section><section>
<h3><a name="Are_there_any_recommendations_on_how_to_handle_dependencies.2C_which_aren.E2.80.99t_always_required.3F"></a>Are there any recommendations on how to handle dependencies, which aren’t always required?</h3>
<p>Create a profile and include the dependency within it. Related document: [http://maven.apache.org/maven-model/maven.html#class_profile]</p></section><section>
<h3><a name="How_to_resolve_problems_with_jtaxxx.jar.3F"></a>How to resolve problems with jtaxxx.jar?</h3>
@@ -1508,7 +1508,7 @@ Wagon wagon;
</section><section>
<h3><a name="I_don.E2.80.99t_have_a_domain_name_and_I_don.E2.80.99t_want_use_my_employer.E2.80.99s_domain_name._What_should_I_name_my_plugin_package.3F"></a>I don’t have a domain name and I don’t want use my employer’s domain name. What should I name my plugin package?</h3>
<p>How will the plugin be licensed? Is it intended to just be a binary distribution or will the source be available? Where will be the documentation be? How will people find out about it? I think your choice is probably influenced by these questions. One option, of course, is to propose it to mojo.codehaus.org if you want to and can share the code.</p></section><section>
-<h3><a name="I_issued_mvn_-Declipse.downloadSources.3Dtrue_eclipse_eclipse_goal._It_created_.classpath_and_.project_for_both_modules.2C_and_in_my_local_repository_it_downloaded_sources_Ho_do_I_access_them_in_eclipse.3F"></a>I issued mvn -Declipse.downloadSources=true eclipse eclipse goal. It created .classpath and .project for both modules, and in my local repository it downloaded sources Ho do I access them in eclipse?</h3>
+<h3><a name="I_issued_mvn_-Declipse.downloadSources.3Dtrue_eclipse_eclipse_goal._It_created_.classpath_and_.project_for_both_modules.2C_and_in_my_local_repository_it_downloaded_sources_Ho_do_I_access_them_in_eclipse.3F"></a>I issued <code>mvn -Declipse.downloadSources=true eclipse eclipse</code> goal. It created .classpath and .project for both modules, and in my local repository it downloaded sources Ho do I access them in eclipse?</h3>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><build>
@@ -1561,14 +1561,14 @@ Wagon wagon;
<h3><a name="I_would_like_clarification_on_what_version_of_the_JDK_is_required_for_m2_-_particularly_with_respect_to_creating_Plugins."></a>I would like clarification on what version of the JDK is required for m2 - particularly with respect to creating Plugins.</h3>
<p>1.4 is required to run m2 there’re problems when using 1.5 features in plugins. People tried and failed because qdox (used for some mojo stuff doesn’t support new 1.5 language)</p></section><section>
<h3><a name="i.E2.80.99m_wondering_what_a_.E2.80.9Csnapshot.E2.80.9D_actually_is."></a>i’m wondering what a “snapshot” actually is.</h3>
-<p>A snapshot is a development version. e.g, 2.0-SNAPSHOT is thestill-in-development future 2.0.If you want to use a snapshot, just use <version> , e.g. <version>2.0-SNAPSHOT</version> . But first you must ensure that you have access to the repository containing this version.</p></section><section>
+<p>A snapshot is a development version. e.g, 2.0-SNAPSHOT is thestill-in-development future 2.0.If you want to use a snapshot, just use <code><version></code> , e.g. <code><version>2.0-SNAPSHOT</version></code> . But first you must ensure that you have access to the repository containing this version.</p></section><section>
<h3><a name="Is_it_possible_that_if_I_do_mvn_eclipse_eclipse_goal_that_my_project_would_get_disconnected_from_the_subversion_repository.3F"></a>Is it possible that if I do mvn eclipse eclipse goal that my project would get disconnected from the subversion repository?</h3>
<p>1.4 is required to run m2 there’re problems when using 1.5 features in plugins. People tried and failed because qdox (used for some mojo stuff doesn’t support new 1.5 language)</p></section><section>
<h3><a name="Does_it_matter_if_the_project.E2.80.99s_directory_name_is_not_the_same_as_the_artifactId.3F"></a>Does it matter if the project’s directory name is not the same as the artifactId?</h3>
<p>It does not really matter. It’ll work, some defaults might have to be overridden (eg SCM inheritance, though that’s hopefully going to change), and the parent path if not.</p></section><section>
<h3><a name="pom.xml_or_settings.xml.3F_What_is_the_best_practice_configuration_usage_for_these_files.3F"></a>pom.xml or settings.xml? What is the best practice configuration usage for these files?</h3>
<p>The best practice guideline between settings.xml and pom.xml is that configurations in settings.xml must be specific to the current user and that pom.xml configurations are specific to the project.</p>
-<p>For example, <repositories> in pom.xml would tell all users of the project to use the <repositories> specified in the pom.xml. However, some users may prefer to use a mirror instead, so they’ll put <mirrors> in their settings.xml so they can choose a faster repository server.</p>
+<p>For example, <code><repositories></code> in pom.xml would tell all users of the project to use the <code><repositories></code> specified in the pom.xml. However, some users may prefer to use a mirror instead, so they’ll put <code><mirrors></code> in their settings.xml so they can choose a faster repository server.</p>
<p>so there you go:</p>
<div class="source">
@@ -1583,7 +1583,7 @@ pom.xml > project scope
<p>To solve this, add <i><i>-Djava.net.preferIPv4Stack=true{</i>}</i> to your maven invocation, i.e. {color:#ff0000}mvn install -Djava.net.preferIPv4Stack=true{color}</p>
<p>More information can be found at [http://wiki.astrogrid.org/bin/view/Deploy/IPV6Warning?skin=print]</p></section><section>
<h3><a name="What_is_a_Snapshot.3F"></a>What is a Snapshot?</h3>
-<p>A snapshot is a development version. e.g, 2.0-SNAPSHOT is the still-in-development future 2.0. If you want to use a snapshot, juste use <version> , e.g. <version>2.0-SNAPSHOT</version>. But first you must ensure that you have access to the repository containing this version. For example, for Maven snapshots as stated below, you could use :</p>
+<p>A snapshot is a development version. e.g, 2.0-SNAPSHOT is the still-in-development future 2.0. If you want to use a snapshot, juste use <code><version></code> , e.g. <code><version>2.0-SNAPSHOT</version></code>. But first you must ensure that you have access to the repository containing this version. For example, for Maven snapshots as stated below, you could use :</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><repositories>
@@ -1725,8 +1725,8 @@ private String version;
</properties>
</pre></div></div>
-<p>Then $myproperty=propertyvalue</p></section><section>
-<h3><a name="How_do_replace_.3CattainGoal.3E_from_m1_in_m2.3F"></a>How do replace <attainGoal> from m1 in m2?</h3>
+<p>Then <code>$myproperty=propertyvalue</code></p></section><section>
+<h3><a name="How_do_replace_.3CattainGoal.3E_from_m1_in_m2.3F"></a>How do replace <code><attainGoal></code> from m1 in m2?</h3>
<p>I want to build a plugin with multiple goal, some goal might be aliases and call other goals. How do i do that in m2?</p></section><section>
<h3><a name="Maven_Open_Source.21_How_do_I_download_the_source_code.3F"></a>Maven Open Source! How do I download the source code?</h3>
<p>I’ve seen the link to the source code: [http://svn.apache.org/repos/asf/maven/components/trunk/]</p>
@@ -1735,7 +1735,7 @@ private String version;
<h3><a name="Why_do_I_get_java.lang.NoClassDefFoundError:_org.2Fcodehaus.2Fclassworlds.2FLauncher_when_I_try_to_execute_Maven.3F"></a>Why do I get java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher when I try to execute Maven?</h3>
<p>This sometimes happens when $M2_HOME is not the same as your $PATH. That is, when ‘which mvn’ does not match $M2_HOME/bin/mvn.</p></section><section>
<h3><a name="How_to_encrypt_a_secure_password_that_includes_an_Ampersand"></a>How to encrypt a secure password that includes an Ampersand</h3>
-<p>If you want to mvn --encrypt-password a password with an ampersand you will get an error, e.g. mvn --encrypt-password test&Password On the one hand the ampersand has to be encoded as entity with &. On the other hand the ampersand has to be escaped for the command line. Result would be mvn --encrypt-password test &Password Also a dollar sign $ has to be escaped for the command line.</p></section></section>
+<p>If you want to <code>mvn --encrypt-password</code> a password with an ampersand you will get an error, e.g. <code>mvn --encrypt-password test&Password</code> On the one hand the ampersand has to be encoded as entity with &. On the other hand the ampersand has to be escaped for the command line. Result would be <code>mvn --encrypt-password test &Password</code> Also a dollar sign $ has to be escaped for the command line.</p></section></section>
</main>
</div>
</div>
Modified: maven/website/content/glossary.html
==============================================================================
--- maven/website/content/glossary.html (original)
+++ maven/website/content/glossary.html Tue Mar 10 19:55:25 2020
@@ -159,7 +159,7 @@ sometimes be confusing for newcomers.
</li>
<li>
-<p><b>GroupId</b>: A group ID is a universally unique identifier for a project. While this is often just the project name (eg. commons-collections), it is helpful to use a fully-qualified package name to distinguish it from other projects with a similar name (eg. org.apache.maven).</p>
+<p><b>GroupId</b>: A group ID is a universally unique identifier for a project. While this is often just the project name (eg. <code>commons-collections</code>), it is helpful to use a fully-qualified package name to distinguish it from other projects with a similar name (eg. <code>org.apache.maven</code>).</p>
</li>
<li>
@@ -180,8 +180,8 @@ sometimes be confusing for newcomers.
</li>
<li>
-<p><b>Snapshots</b>: Projects can (and should) have a special version including SNAPSHOT to indicate that they are a “work in progress”, and are not yet released. When a snapshot dependency is encountered, it is always looked for in all remote repositories, and downloaded again if newer than the local copy.</p>
-<p>The version can either be the string SNAPSHOT itself, indicating “the very latest” development version, or something like 1.1-SNAPSHOT, indicating development that will be released as 1.1 (i.e. newer than 1.0, but not yet 1.1).</p>
+<p><b>Snapshots</b>: Projects can (and should) have a special version including <code>SNAPSHOT</code> to indicate that they are a “work in progress”, and are not yet released. When a snapshot dependency is encountered, it is always looked for in all remote repositories, and downloaded again if newer than the local copy.</p>
+<p>The version can either be the string <code>SNAPSHOT</code> itself, indicating “the very latest” development version, or something like <code>1.1-SNAPSHOT</code>, indicating development that will be released as 1.1 (i.e. newer than 1.0, but not yet 1.1).</p>
</li>
<li>
Modified: maven/website/content/install.html
==============================================================================
--- maven/website/content/install.html (original)
+++ maven/website/content/install.html Tue Mar 10 19:55:25 2020
@@ -153,7 +153,7 @@ and adding the `bin` folder with the `mv
<li>
-<p>Ensure JAVA_HOME environment variable is set and points to your JDK installation</p>
+<p>Ensure <code>JAVA_HOME</code> environment variable is set and points to your JDK installation</p>
</li>
<li>
@@ -176,11 +176,11 @@ and adding the `bin` folder with the `mv
<li>
-<p>Add the bin directory of the created directory apache-maven-3.6.3 to the PATH environment variable</p>
+<p>Add the <code>bin</code> directory of the created directory <code>apache-maven-3.6.3</code> to the <code>PATH</code> environment variable</p>
</li>
<li>
-<p>Confirm with mvn -v in a new shell. The result should look similar to</p>
+<p>Confirm with <code>mvn -v</code> in a new shell. The result should look similar to</p>
</li>
</ul>
@@ -208,11 +208,11 @@ C:\Program Files\Java\jdk1.7.0_51
<li>
-<p>Adding to PATH: Add the unpacked distribution’s bin directory to your user PATH environment variable by opening up the system properties (WinKey + Pause), selecting the “Advanced” tab, and the “Environment Variables” button, then adding or selecting the <i>PATH</i> variable in the user variables with the value C:\Program Files\apache-maven-3.6.3\bin. The same dialog can be used to set JAVA_HOME to the location of your JDK, e.g. C:\Program Files\Java\jdk1.7.0_51</p>
+<p>Adding to <code>PATH</code>: Add the unpacked distribution’s bin directory to your user PATH environment variable by opening up the system properties (WinKey + Pause), selecting the “Advanced” tab, and the “Environment Variables” button, then adding or selecting the <i>PATH</i> variable in the user variables with the value <code>C:\Program Files\apache-maven-3.6.3\bin</code>. The same dialog can be used to set <code>JAVA_HOME</code> to the location of your JDK, e.g. <code>C:\Program Files\Java\jdk1.7.0_51</code></p>
</li>
<li>
-<p>Open a new command prompt (Winkey + R then type cmd) and run mvn -v to verify the installation.</p>
+<p>Open a new command prompt (Winkey + R then type <code>cmd</code>) and run <code>mvn -v</code> to verify the installation.</p>
</li>
</ul></section><section>
<h2><a name="Unix-based_Operating_System_.28Linux.2C_Solaris_and_Mac_OS_X.29_Tips"></a>Unix-based Operating System (Linux, Solaris and Mac OS X) Tips</h2>
@@ -228,7 +228,7 @@ C:\Program Files\Java\jdk1.7.0_51
<ul>
-<li>Adding to PATH</li>
+<li>Adding to <code>PATH</code></li>
</ul>
<div class="source">
Modified: maven/website/content/maven-ci-friendly.html
==============================================================================
--- maven/website/content/maven-ci-friendly.html (original)
+++ maven/website/content/maven-ci-friendly.html Tue Mar 10 19:55:25 2020
@@ -160,7 +160,7 @@ and/or `${changelist}` as placeholders f
</project>
</pre></div></div>
-<p>This is of course a simple situation where we use only ${revision} for brevity to show the general course.</p>
+<p>This is of course a simple situation where we use only <code>${revision}</code> for brevity to show the general course.</p>
<p>Based on the above pom you can build your project using:</p>
<div class="source">
@@ -194,15 +194,15 @@ and/or `${changelist}` as placeholders f
</project>
</pre></div></div>
-<p>So now you can simply call Maven as usual like mvn clean package.</p>
+<p>So now you can simply call Maven as usual like <code>mvn clean package</code>.</p>
<p>You can of course change the version via the command line like this:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">mvn -Drevision=2.0.0-SNAPSHOT clean package
</pre></div></div>
-<p>Of course you can use the .mvn/maven.config file for this.</p>
-<p>A note about the used properties. You can only use those named ${revision}, ${sha1} and/or ${changelist} and not other named properties like this:</p>
+<p>Of course you can use the <code>.mvn/maven.config</code> file for this.</p>
+<p>A note about the used properties. You can only use those named <code>${revision}</code>, <code>${sha1}</code> and/or <code>${changelist}</code> and not other named properties like this:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><project>
@@ -246,7 +246,7 @@ and/or `${changelist}` as placeholders f
</project>
</pre></div></div>
-<p>If you like to make a version 2.0.0-SNAPSHOT this can simply being achieved by using this:</p>
+<p>If you like to make a version <code>2.0.0-SNAPSHOT</code> this can simply being achieved by using this:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">mvn -Drevision=2.0.0 clean package
@@ -307,9 +307,9 @@ and/or `${changelist}` as placeholders f
</project>
</pre></div></div>
-<p>A multi module build can of course build the same way as the single project setup. You should define the version either via property in the parent or use the .mvn/maven.config file.</p></section><section>
+<p>A multi module build can of course build the same way as the single project setup. You should define the version either via property in the parent or use the <code>.mvn/maven.config</code> file.</p></section><section>
<h2><a name="Dependencies"></a>Dependencies</h2>
-<p>In a multi module build you have often the case that you define dependencies between module(s). The usual way of defining dependencies and their appropriate versions has been to use ${project.version} and this has not been changed.</p>
+<p>In a multi module build you have often the case that you define dependencies between module(s). The usual way of defining dependencies and their appropriate versions has been to use <code>${project.version}</code> and this has not been changed.</p>
<p>So the correct way to do such things can be seen in the following example:</p>
<div class="source">
@@ -358,7 +358,7 @@ and/or `${changelist}` as placeholders f
</project>
</pre></div></div>
-<p>If you try to use ${revision} instead of ${project.version} your build will fail.</p></section><section>
+<p>If you try to use <code>${revision}</code> instead of <code>${project.version}</code> your build will fail.</p></section><section>
<h2><a name="Install_.2F_Deploy"></a>Install / Deploy</h2>
<p>If you like to install or deploy artifacts by using the above setup you <b>have to use</b> the <a class="externalLink" href="https://www.mojohaus.org/flatten-maven-plugin/">flatten-maven-plugin</a> otherwise you will install/deploy artifacts in your repository which will not be consumable by Maven anymore. Such kind of setup will look like this:</p>
Modified: maven/website/content/maven-jsr330.html
==============================================================================
--- maven/website/content/maven-jsr330.html (original)
+++ maven/website/content/maven-jsr330.html Tue Mar 10 19:55:25 2020
@@ -176,11 +176,11 @@ under the License.
<li>
-<p>First you want a dependency on javax.inject so you can use the @Inject, @Named, and @Singleton annotations in your plugins and extensions.</p>
+<p>First you want a dependency on <code>javax.inject</code> so you can use the <code>@Inject</code>, <code>@Named</code>, and <code>@Singleton</code> annotations in your plugins and extensions.</p>
</li>
<li>
-<p>Second you need to setup the <a class="externalLink" href="https://eclipse.org/sisu/docs/api/org.eclipse.sisu.mojos/">sisu-maven-plugin</a> to index the JSR-330 components you want made available to Maven. The sisu-maven-plugin creates its index in META-INF/sisu/javax.inject.Named.</p>
+<p>Second you need to setup the <a class="externalLink" href="https://eclipse.org/sisu/docs/api/org.eclipse.sisu.mojos/"><code>sisu-maven-plugin</code></a> to index the JSR-330 components you want made available to Maven. The <code>sisu-maven-plugin</code> creates its index in <code>META-INF/sisu/javax.inject.Named</code>.</p>
</li>
</ol>
<p>If you take a look in that file with the example from the next paragraph, you will see something like the following:</p>
@@ -246,7 +246,7 @@ org.apache.maven.lifecycle.profiler.inte
</project>
</pre></div></div>
-<p>So, as mentioned, we have the javax.inject dependency and the sisu-maven-plugin configured to create the JSR-330 component index. When you build and place the extension JAR in the ${MAVEN_HOME}/lib/ext folder, it will automatically get picked up by Maven. In the case of this example, we have an implementation of an EventSpy that times the executions of individual mojos within a phase in the lifecycle.</p>
+<p>So, as mentioned, we have the <code>javax.inject</code> dependency and the <code>sisu-maven-plugin</code> configured to create the JSR-330 component index. When you build and place the extension JAR in the <code>${MAVEN_HOME}/lib/ext</code> folder, it will automatically get picked up by Maven. In the case of this example, we have an implementation of an <code>EventSpy</code> that times the executions of individual mojos within a phase in the lifecycle.</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">package org.apache.maven.lifecycle.profiler;
@@ -340,7 +340,7 @@ public class LifecycleProfiler extends A
</pre></div></div>
</section><section>
<h2><a name="How_to_use_JSR-330_in_plugins"></a>How to use JSR-330 in plugins</h2>
-<p>Let's take a look at an example plugin. The POM is setup in a similar way to an extension, but we add a dependency to maven-plugin-api and maven-plugin-annotations to extend the AbstractMojo and use the Java 5 plugin annotations in our example.</p>
+<p>Let's take a look at an example plugin. The POM is setup in a similar way to an extension, but we add a dependency to <code>maven-plugin-api</code> and <code>maven-plugin-annotations</code> to extend the <code>AbstractMojo</code> and use the Java 5 plugin annotations in our example.</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -428,7 +428,7 @@ public class LifecycleProfiler extends A
</project>
</pre></div></div>
-<p>Now let's take a look at the plugin code. You'll notice that we're using constructor injection which makes testing a lot easier. If you want to test your Jsr330Component, you do not need the container to instantiate the Mojo. In this simple case, you can actually test this plugin without using the plugin testing harness because you can instantiate the Jsr330Component and Jsr330Mojo directly and wire everything up manually using the constructor. Constructor injection, which Plexus lacks, greatly simplifies testing.</p>
+<p>Now let's take a look at the plugin code. You'll notice that we're using constructor injection which makes testing a lot easier. If you want to test your <code>Jsr330Component</code>, you do not need the container to instantiate the <code>Mojo</code>. In this simple case, you can actually test this plugin without using the plugin testing harness because you can instantiate the <code>Jsr330Component</code> and <code>Jsr330Mojo</code> directly and wire everything up manually using the constructor. Constructor injection, which Plexus lacks, greatly simplifies testing.</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">package org.apache.maven.plugins;
Modified: maven/website/content/maven-logging.html
==============================================================================
--- maven/website/content/maven-logging.html (original)
+++ maven/website/content/maven-logging.html Tue Mar 10 19:55:25 2020
@@ -143,7 +143,7 @@ to stdout.
<p>We have reached the decision that <a class="externalLink" href="http://slf4j.org">SLF4J</a> is the best option for a logging API: SLF4J has reached a certain level of ubiquity and while SLF4J may not be perfect, it's the de facto standard and it's pointless to try and remake another one. There are many implementations to choose from, including <a class="externalLink" href="http://logback.qos.ch">Logback</a> and <a class="externalLink" href="https://logging.apache.org/log4j/2.x/log4j-slf4j-impl/">Log4j2</a>. All the hard work has been done. All the bridges and funnels for other systems function well, which allows others to use whatever logging implementation they like in their components, while still being able to have integrated logging.</p>
<p>The standard Maven distribution, from Maven 3.1.0 onward, uses the <a class="externalLink" href="http://slf4j.org/apidocs/">SLF4J API</a> for logging combined with the <a class="externalLink" href="http://www.slf4j.org/apidocs/org/slf4j/impl/SimpleLogger.html">SLF4J Simple</a> implementation. Future versions may use a more advanced implementation, but we chose to start simple.</p>
-<p>Looking at the distribution you will see the following layout where the simplelogger.properties, slf4j-api-x.y.z-jar and slf4j-simple-x.y.z.jar specifically relate to the SLF4J implementation:</p>
+<p>Looking at the distribution you will see the following layout where the <code>simplelogger.properties</code>, <code>slf4j-api-x.y.z-jar</code> and <code>slf4j-simple-x.y.z.jar</code> specifically relate to the SLF4J implementation:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">
@@ -167,11 +167,11 @@ apache-maven-3.x.y
</pre></div></div>
<section>
<h2><a name="Configuring_logging"></a>Configuring logging</h2>
-<p>To configure logging with the <a class="externalLink" href="http://www.slf4j.org/apidocs/org/slf4j/impl/SimpleLogger.html">SLF4J Simple</a>, you can edit the properties in the ${maven.home}/conf/logging/simplelogger.properties file. Please see the linked reference documentation for details.</p>
-<p>Every entry in this file can be overriden via Maven’s JVM system properties by using the -D flag in <a class="externalLink" href="https://maven.apache.org/configure.html">MAVEN_OPTS</a>. E.g. MAVEN_OPTS=-Dorg.slf4j.simpleLogger.showThreadName=true mvn <goals> will add the thread name to every logging line.</p>
+<p>To configure logging with the <a class="externalLink" href="http://www.slf4j.org/apidocs/org/slf4j/impl/SimpleLogger.html">SLF4J Simple</a>, you can edit the properties in the <code>${maven.home}/conf/logging/simplelogger.properties</code> file. Please see the linked reference documentation for details.</p>
+<p>Every entry in this file can be overriden via Maven’s JVM system properties by using the <code>-D</code> flag in <a class="externalLink" href="https://maven.apache.org/configure.html">MAVEN_OPTS</a>. E.g. <code>MAVEN_OPTS=-Dorg.slf4j.simpleLogger.showThreadName=true mvn <goals></code> will add the thread name to every logging line.</p>
<p>The default SLF4J configuration for Maven is listed <a class="externalLink" href="https://github.com/apache/maven/blob/master/apache-maven/src/conf/logging/simplelogger.properties">here</a>.</p></section><section>
<h2><a name="Changing_the_SLF4J_implementation"></a>Changing the SLF4J implementation</h2>
-<p>If you want use a different logging implementation it is simply a matter of removing the slf4j-simple JAR from the lib directory and replacing it with one of the alternative implementations, like <a class="externalLink" href="https://logging.apache.org/log4j/2.x/log4j-slf4j-impl/">Log4j2</a> or <a class="externalLink" href="http://logback.qos.ch">Logback</a>.</p>
+<p>If you want use a different logging implementation it is simply a matter of removing the slf4j-simple JAR from the <code>lib</code> directory and replacing it with one of the alternative implementations, like <a class="externalLink" href="https://logging.apache.org/log4j/2.x/log4j-slf4j-impl/">Log4j2</a> or <a class="externalLink" href="http://logback.qos.ch">Logback</a>.</p>
<p>See SLF4J documentation for more details on <a class="externalLink" href="http://www.slf4j.org/manual.html#swapping">swapping “SLF4J bindings”</a>.</p></section>
</main>
</div>
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified: maven/website/content/project-info.html
==============================================================================
--- maven/website/content/project-info.html (original)
+++ maven/website/content/project-info.html Tue Mar 10 19:55:25 2020
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.1 from org.apache.maven.plugins:maven-site-plugin:3.8.2:CategorySummaryDocumentRenderer at 2020-03-10
+ | Generated by Apache Maven Doxia Site Renderer 1.9.1 from org.apache.maven.plugins:maven-site-plugin:3.9.0:CategorySummaryDocumentRenderer at 2020-03-10
| Rendered using Apache Maven Fluido Skin 1.8
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
Modified: maven/website/content/reference/maven-classloading.html
==============================================================================
--- maven/website/content/reference/maven-classloading.html (original)
+++ maven/website/content/reference/maven-classloading.html Tue Mar 10 19:55:25 2020
@@ -142,15 +142,15 @@ under the License.
<section>
<h2><a name="ClassWorlds_bootstrap_classloader"></a>ClassWorlds bootstrap classloader</h2>
<p>This classloader is created and managed by the calling environment: JVM launcher, integration testing harness, etc.</p>
-<p>During normal command line Maven invocation this is the JVM System classloader and contains classes from ${maven.home}/boot/plexus-classworlds-*.jar and classes from -javaagent.</p></section><section>
+<p>During normal command line Maven invocation this is the JVM System classloader and contains classes from <code>${maven.home}/boot/plexus-classworlds-*.jar</code> and classes from <code>-javaagent</code>.</p></section><section>
<h2><a name="Maven_Core_classloader"></a>Maven Core classloader</h2>
<p>This classloader contains core Maven runtime classes like MavenProject, AsbtractMojo and so on. This is the classloader set as the “container realm” in the Plexus container instance unless Maven Extensions classloader is created (see below).</p>
-<p>Contents of this classloader are configured in ${maven.home}/bin/m2.conf and typically contains ${maven.home}/lib/ext/*.jar and ${maven.home}/lib/*.jar.</p></section><section>
+<p>Contents of this classloader are configured in <code>${maven.home}/bin/m2.conf</code> and typically contains <code>${maven.home}/lib/ext/*.jar</code> and <code>${maven.home}/lib/*.jar</code>.</p></section><section>
<h2><a name="Maven_Core_Extensions_classloaders"></a>Maven Core Extensions classloaders</h2>
<p>Core Extensions is a new mechanism introduced in Maven 3.3.0 which allows additional components to be loaded into Maven Core as part of a build session.</p>
<p>Each core extension is loaded in a separate classloader and there is no mechanism to share classes among core extensions. Core extensions classloaders use Maven Core classloader as the parent and have access to both exported and internal Maven Core classes.</p>
-<p>Core extension can use META-INF/maven/extension.xml descriptor to declare packages and artifacts exported by the extension. If the descriptor is not present, no packages or artifacts are exported, but the extension can still contribute components to Maven Core extension points.</p>
-<p>Core extensions are configured in ${maven.projectBasedir}/.mvn/extensions.xml configuration file.</p>
+<p>Core extension can use <code>META-INF/maven/extension.xml</code> descriptor to declare packages and artifacts exported by the extension. If the descriptor is not present, no packages or artifacts are exported, but the extension can still contribute components to Maven Core extension points.</p>
+<p>Core extensions are configured in <code>${maven.projectBasedir}/.mvn/extensions.xml</code> configuration file.</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><?xml version="1.0" encoding="UTF-8"?>
@@ -167,27 +167,27 @@ under the License.
<p>Core extensions are loaded as part of Maven runtime startup and disposed of as part of Maven runtime shutdown.</p></section><section>
<h2><a name="Maven_extensions_classloader"></a>Maven extensions classloader</h2>
-<p>Maven extensions classloader aggregates packages exported by core extensions realms. It also loads additional classpath entries specified in -Dmaven.ext.class.path command line parameter.</p>
+<p>Maven extensions classloader aggregates packages exported by core extensions realms. It also loads additional classpath entries specified in <code>-Dmaven.ext.class.path</code> command line parameter.</p>
<p>Maven extensions classloader is created only when core extensions are configured for the build. If created, it will be set as “container realm” in the Plexus container.</p></section><section>
<h2><a name="Maven_API_classloader"></a>Maven API classloader</h2>
<p>Maven API classloader aggregates exported packages from Maven Core and Maven Core Extensions classloaders. Maven API classloader does not include any classes directly.</p>
-<p>Maven API uses approximate JVM Bootstrap classloader as its parent. (there is no API to access JVM Bootstrap classloader, implementation uses ClassLoader.getSystemClassLoader().getParent()). The parent classloader does not contain any application or javaagent classes, which allows for consistent Maven API classpath regardless how Maven JVM was launched.</p></section><section>
+<p>Maven API uses approximate JVM Bootstrap classloader as its parent. (there is no API to access JVM Bootstrap classloader, implementation uses <code>ClassLoader.getSystemClassLoader().getParent()</code>). The parent classloader does not contain any application or javaagent classes, which allows for consistent Maven API classpath regardless how Maven JVM was launched.</p></section><section>
<h2><a name="Build_Extension_classloaders"></a>Build Extension classloaders</h2>
-<p>Modern Maven 3.x build extensions are build extensions that either consist of multiple artifacts or have META-INF/maven/extension.xml. Each modern build extension is loaded in a a fully isolated classloader, i.e. it is not possible to share classes or inject components among extensions.</p>
+<p>Modern Maven 3.x build extensions are build extensions that either consist of multiple artifacts or have <code>META-INF/maven/extension.xml</code>. Each modern build extension is loaded in a a fully isolated classloader, i.e. it is not possible to share classes or inject components among extensions.</p>
<p>Maven guarantees that each distinct modern build extension (as identified by plugin groupId, artifactId, version and set of dependecies) is loaded by one and only one extensions classloader and the classloader is wired to all projects that use the extension.</p>
-<p>Build extension classloaders use ClassWorld bootstrap classloader as the parent, which allows build extensions access to -javaagent classes.</p></section><section>
+<p>Build extension classloaders use ClassWorld bootstrap classloader as the parent, which allows build extensions access to <code>-javaagent</code> classes.</p></section><section>
<h2><a name="Project_classloaders"></a>Project classloaders</h2>
<p>Project classloader aggregates Maven API packages, packages exported by project build extensions.</p>
-<p>Project classloaders use Maven API classloader as the parent and import exported classes from project build extension realms. Legacy Maven 2.x build extensions, i.e. extensions that consist of single artifact which does not include META-INF/maven/extension.xml descriptor, are directly in project classloaders.</p>
+<p>Project classloaders use Maven API classloader as the parent and import exported classes from project build extension realms. Legacy Maven 2.x build extensions, i.e. extensions that consist of single artifact which does not include <code>META-INF/maven/extension.xml</code> descriptor, are directly in project classloaders.</p>
<p>Maven guarantees there will be one and only one project classloader for each unique set of project build extensions and the same classloader will be used by all projects that have the set of build extensions.</p></section><section>
<h2><a name="Plugin_classloaders"></a>Plugin classloaders</h2>
<p>Plugin classloaders are wired differently for projects with and without build extensions.</p>
<p>For projects without build extensions, single classloader is created for each plugin identified by groupId:artifactId:version and the classloader imports API packages from Maven API classloader. Maven will create one and only one classloader for each unique plugin+dependency combination.</p>
<p>For projects that use build extensions, plugin classloaders are wired to project classloaders. This gives plugin code access to both Maven API packages and packages exported by the project build extensions. Maven will create one and only one classlaoder for each unique plugin+dependencies+build-extensions combination.</p>
-<p>All plugin classloaders use ClassWorlds bootstrap classloader as the parent. This provides relatively clean and therefore consistent plugin classpath, while still allowing plugins access to -javaagent classes (see <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-4747">MNG-4747</a>).</p>
+<p>All plugin classloaders use ClassWorlds bootstrap classloader as the parent. This provides relatively clean and therefore consistent plugin classpath, while still allowing plugins access to <code>-javaagent</code> classes (see <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-4747">MNG-4747</a>).</p>
<p>Reporting plugins are wired differently still, but reporting plugins are a special case and are outside of the scope of this document.</p></section><section>
<h2><a name="Exported_artifacts_and_packages"></a>Exported artifacts and packages</h2>
-<p>Maven Core, Session and Build Extensions use META-INF/maven/extension.xml descriptor to declare API packages and artifacts exported by the classloader.</p>
+<p>Maven Core, Session and Build Extensions use <code>META-INF/maven/extension.xml</code> descriptor to declare API packages and artifacts exported by the classloader.</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums"><?xml version="1.0" encoding="UTF-8"?>