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 bu...@apache.org on 2014/07/11 07:10:39 UTC
svn commit: r915746 [8/13] - in /websites/staging/maven/trunk/content: ./
apache-resource-bundles/ archives/maven-2.x/ background/ developers/
developers/conventions/ developers/release/ developers/website/ docs/
docs/2.0.1/ docs/2.0.10/ docs/2.0.11/ d...
Modified: websites/staging/maven/trunk/content/guides/mini/guide-creating-archetypes.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-creating-archetypes.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-creating-archetypes.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Creating Archetypes</title>
+ <title>Maven – Guide to Creating Archetypes</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -14,7 +14,7 @@
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Jason van Zyl, Alexander Hars, Franz Allan Valencia See" />
<meta name="Date-Creation-yyyymmdd" content="20100410" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -44,7 +44,7 @@
Guide to Creating Archetypes
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -242,7 +242,7 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Guide to Creating Archetypes<a name="Guide_to_Creating_Archetypes"></a></h2>
+<h2><a name="Guide_to_Creating_Archetypes"></a>Guide to Creating Archetypes</h2>
<p>Creating an archetype is a pretty straight forward process. An archetype is a very simple artifact, that contains the project prototype you wish to create. An archetype is made up of:</p>
<ul>
<li>an <a class="externalLink" href="http://maven.apache.org/archetype/archetype-common/archetype.html">archetype descriptor</a> (<tt>archetype.xml</tt> in directory: <tt>src/main/resources/META-INF/maven/</tt>). It lists all the files that will be contained in the archetype and categorizes them so they can be processed correctly by the archetype generation mechanism.</li>
@@ -252,7 +252,7 @@
<p>Note: this mini-guide has been written for <a class="externalLink" href="http://maven.apache.org/plugins/maven-archetype-plugin-1.0-alpha-7/">archetype plugin version 1.0.x</a>, with its <a class="externalLink" href="http://maven.apache.org/archetype/archetype-common/archetype.html">old archetype descriptor</a> (stored in <tt>archetype.xml</tt> file). <a class="externalLink" href="http://maven.apache.org/archetype/maven-archetype-plugin/">Archetype plugin 2.0.x</a> is a new generation that fully supports archetypes created for 1.0.x, and adds a <a class="externalLink" href="http://maven.apache.org/archetype/archetype-common/archetype-descriptor.html">new archetype descriptor</a> (stored in <tt>archetype-metadata.xml</tt> file): it's more flexible, has more features, but the basis is absolutely the same.</p>
<p>To create an archetype follow these steps:</p>
<div class="section">
-<h3>1. Create a new project and pom.xml for the archetype artifact<a name="a1._Create_a_new_project_and_pom.xml_for_the_archetype_artifact"></a></h3>
+<h3><a name="a1._Create_a_new_project_and_pom.xml_for_the_archetype_artifact"></a>1. Create a new project and pom.xml for the archetype artifact</h3>
<p>An example <tt>pom.xml</tt> for an archetype artifact looks as follows:</p>
<div class="source">
<pre>
@@ -268,7 +268,7 @@
</pre></div>
<p>All you need to specify is a <tt>groupId</tt>, <tt>artifactId</tt> and <tt>version</tt>. These three parameters will be needed later for invoking the archetype via <tt>archetype:generate</tt> from the commandline.</p></div>
<div class="section">
-<h3>2. Create the archetype descriptor<a name="a2._Create_the_archetype_descriptor"></a></h3>
+<h3><a name="a2._Create_the_archetype_descriptor"></a>2. Create the archetype descriptor</h3>
<p>The <a class="externalLink" href="http://maven.apache.org/archetype/archetype-common/archetype.html">archetype descriptor</a> is a file called <tt>archetype.xml</tt> which must be located in the <tt>src/main/resources/META-INF/maven/</tt> directory. An example of an archetype descriptor can be found in the quickstart archetype:</p>
<div class="source">
<pre>
@@ -318,7 +318,7 @@ archetype
`-- AppTest.java
</pre></div></div>
<div class="section">
-<h3>3. Create the prototype files and the prototype pom.xml<a name="a3._Create_the_prototype_files_and_the_prototype_pom.xml"></a></h3>
+<h3><a name="a3._Create_the_prototype_files_and_the_prototype_pom.xml"></a>3. Create the prototype files and the prototype pom.xml</h3>
<p>The next component of the archetype to be created is the prototype <tt>pom.xml</tt>. Any <tt>pom.xml</tt> will do, just don't forget to the set <tt>artifactId</tt> and <tt>groupId</tt> as variables ( <tt>${artifactId}</tt> / <tt>${groupId}</tt> ). Both variables will be initialized from the commandline when calling <tt>archetype:generate</tt>.</p>
<p>An example for a prototype <tt>pom.xml</tt> is:</p>
<div class="source">
@@ -346,7 +346,7 @@ archetype
</project>
</pre></div></div>
<div class="section">
-<h3>4. Install the archetype and run the archetype plugin<a name="a4._Install_the_archetype_and_run_the_archetype_plugin"></a></h3>
+<h3><a name="a4._Install_the_archetype_and_run_the_archetype_plugin"></a>4. Install the archetype and run the archetype plugin</h3>
<p>Now you are ready to install the archetype:</p>
<div class="source">
<pre>
@@ -364,7 +364,7 @@ mvn archetype:generate
</pre></div>
<p>Once you are happy with the state of your archetype, you can deploy (or submit it to ibiblio) it as any other artifact and the archetype will then be available to any user of Maven.</p></div>
<div class="section">
-<h3>Alternative way to start creating your Archetype<a name="Alternative_way_to_start_creating_your_Archetype"></a></h3>
+<h3><a name="Alternative_way_to_start_creating_your_Archetype"></a>Alternative way to start creating your Archetype</h3>
<p>Instead of manually creating the directory structure needed for an archetype, simply use</p>
<div class="source">
<pre>mvn archetype:generate
Modified: websites/staging/maven/trunk/content/guides/mini/guide-default-execution-ids.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-default-execution-ids.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-default-execution-ids.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Configuring Default Mojo Executions</title>
+ <title>Maven – Guide to Configuring Default Mojo Executions</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="John Casey" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Guide to Configuring Default Mojo Executions
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -241,7 +241,7 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Guide to Configuring Default Mojo Executions<a name="Guide_to_Configuring_Default_Mojo_Executions"></a></h2>
+<h2><a name="Guide_to_Configuring_Default_Mojo_Executions"></a>Guide to Configuring Default Mojo Executions</h2>
<p>In most cases where you need to configure a plugin, there are two options that work well: plugin-level configuration and execution-level configuration. Plugin-level configuration is the most common method for configuring plugins that will be used from the command line, are defined as part of the default lifecycle, or that use a common configuration across all invocations. In fact, for direct invocation from the command line, plugin-level configuration has been the <i>only</i> option historically.</p>
<p>On the other hand, in cases where a more advanced build process requires the execution of mojos - sometimes the same mojos, sometimes different ones - from a single plugin that use different configurations, the execution-level configuration is most commonly used. These cases normally involve plugins that are introduced as part of the standard build process, but which aren't present in the default lifecycle mapping for that particular packaging. In these cases, common settings shared between executions are still normally specified in the plugin-level configuration.</p>
<p>However, these two options leave out a few important configuration use cases: </p>
@@ -250,10 +250,10 @@
<p># Groups of mojos from the same plugin that are bound to the lifecycle as part of the default mapping for a particular packaging, but require separate configurations.</p>
<p>Originally, the default value of the executionId - literally set to <tt>default</tt> in the POM model - was meant to provide some of this functionality. Unfortunately, this solution was never tested to make sure it worked with the use cases above; they fell through the cracks during testing. Now, with the release of Maven 2.2.0 (and later, Maven 3.0), these use cases can finally be addressed.</p>
<div class="section">
-<h3>Default <tt>executionId</tt>s for Implied Executions<a name="Default_executionIds_for_Implied_Executions"></a></h3>
+<h3><a name="Default_executionIds_for_Implied_Executions"></a>Default <tt>executionId</tt>s for Implied Executions</h3>
<p>When you consider the fact that the aforementioned configuration use cases are for mojos that are not explicitly mentioned in the POM, it's reasonable to refer to them as implied executions. But if they're implied, how can Maven allow users to provide configuration for them? The solution we've implemented is rather simple and low-tech, but should be more than adequate to handle even advanced use cases. Starting in Maven 2.2.0, each mojo invoked directly from the command line will have an execution Id of <tt>default-cli</tt> assigned to it, which will allow the configuration of that execution from the POM by using this default execution Id. Likewise, each mojo bound to the build lifecycle via the default lifecycle mapping for the specified POM packaging will have an execution Id of <tt>default-<goalName></tt> assigned to it, to allow configuration of each default mojo execution independently.</p>
<div class="section">
-<h4>Example: Command-line variant invocation of the assembly plugin<a name="Example:_Command-line_variant_invocation_of_the_assembly_plugin"></a></h4>
+<h4><a name="Example:_Command-line_variant_invocation_of_the_assembly_plugin"></a>Example: Command-line variant invocation of the assembly plugin</h4>
<p>Consider the case where the user wants to execute the <tt>assembly:assembly</tt> mojo directly on the command line, but already has a configuration for the <tt>assembly:single</tt> mojo that runs during the main build lifecycle. Since these configurations require different options, the user cannot use the plugin-level configuration section to specify common elements.</p>
<p>In this case, the assembly-plugin configuration might look like this:</p>
<div class="source">
@@ -290,7 +290,7 @@
<p>In the above example, you can see several interesting things. First, the main build process will invoke the <tt>assembly:single</tt> mojo during the <tt>package</tt> phase of the build, and produce both binary and source distribution artifacts using custom assembly descriptors included with the project. Second, all invocations of the assembly plugin should use a <tt>tarLongFileMode</tt> strategy of <tt>gnu</tt>. Finally, when the assembly plugin is invoked from the command line, it will build the standard <tt>jar-with-dependencies</tt> and <tt>project</tt> artifacts for the project, and ignore the custom assembly descriptors in <tt>src/main/assembly</tt>.</p>
<p>Now, notice the difference in the way the two execution blocks reference assembly descriptors. One uses custom descriptors via the <tt>descriptors</tt> section, and the other uses standard descriptors via the <tt>descriptorRefs</tt> section. These two sections cannot override one another, so it's impossible to setup one section - say, <tt>descriptorRefs</tt> - in the plugin-level configuration block (to provide CLI access to it, as historical versions of Maven would require), then have the <tt>build-distros</tt> invocation override it with the custom descriptors specified in the <tt>descriptors</tt> section. This configuration is not possible in versions of Maven before 2.2.0.</p></div>
<div class="section">
-<h4>Example: Configuring <tt>compile</tt> to run twice<a name="Example:_Configuring_compile_to_run_twice"></a></h4>
+<h4><a name="Example:_Configuring_compile_to_run_twice"></a>Example: Configuring <tt>compile</tt> to run twice</h4>
<p>In this scenario, the user wants to run the <tt>compiler:compile</tt> mojo twice for his <tt>jar</tt> packaging project. The main reason for this is to provide an entry point into the application that will warn the user if he's using a Java version older than 1.5, then exit gracefully. Without such an entry point, the user would be confronted with a stacktrace in the event he tried to run this application with a 1.4 or older JRE.</p>
<p>Therefore, the user needs to compile tha bulk of his application to target the 1.5 Java specification, then compile the rest (the entry point) to target an older specification...say, 1.3. The first execution will specify the <tt>source</tt> and <tt>target</tt> values at <tt>1.5</tt>, and add an <tt>excludes</tt> section to avoid compiling the entry point for the application. The second pass will then re-specify <tt>source</tt> and <tt>target</tt> to <tt>1.3</tt>, and basically invert the original <tt>excludes</tt> section to be an <tt>includes</tt> section, so as to compile <i>only</i> the entry point class.</p>
<p>The resulting configuration might look something like this:</p>
@@ -332,7 +332,7 @@
<p># The second pass of the <tt>compile</tt> mojo - in the execution called <tt>build-java14-cli</tt> - resets the <tt>source</tt> and <tt>target</tt> versions to <tt>1.3</tt>, and inverts the exclude rule from the first pass. This means the second time around, the compiler will produce 1.4-targeted binaries for the classes matching the <tt>**/cli/*</tt> path pattern.</p>
<p>Note that prior to Maven 2.2.0, it was much more difficult - if not impossible - to compile different subpaths within your project's codebase to target different Java versions.</p></div>
<div class="section">
-<h4>Example: Configuring <tt>compile</tt> and <tt>testCompile</tt> mojos separately<a name="Example:_Configuring_compile_and_testCompile_mojos_separately"></a></h4>
+<h4><a name="Example:_Configuring_compile_and_testCompile_mojos_separately"></a>Example: Configuring <tt>compile</tt> and <tt>testCompile</tt> mojos separately</h4>
<p>Finally, building on our use of the compiler plugin to tease out these different use cases, consider the case where a user wants to target version 1.4 of the Java specification as his runtime platform. However, he still wants the convenience and other advantages to be found in a unit-testing framework like TestNG. This forces the user to configure the <tt>compile</tt> mojo with one set of <tt>source</tt> and <tt>target</tt> values - specifically, <tt>1.4</tt> - and the <tt>testCompile</tt> mojo with another (<tt>1.5</tt>).</p>
<p>The resulting compiler-plugin configuration might look something like the following:</p>
<div class="source">
Modified: websites/staging/maven/trunk/content/guides/mini/guide-deployment-security-settings.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-deployment-security-settings.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-deployment-security-settings.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Deployment and Security Settings</title>
+ <title>Maven – Guide to Deployment and Security Settings</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Jason van Zyl" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Guide to Deployment and Security Settings
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -241,7 +241,7 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Security and Deployment Settings<a name="Security_and_Deployment_Settings"></a></h2>
+<h2><a name="Security_and_Deployment_Settings"></a>Security and Deployment Settings</h2>
<p>Repositories to deploy to are defined in a project in the <tt>distributionManagement</tt> section. However, you cannot put your username, password, or other security settings in that project. For that reason, you should add a server definition to your own settings with an id that matches that of the deployment repository in the project.</p>
<p>In addition, some repositories may require authorisation to download from, so the corresponding settings can be specified in a server element in the same way.</p>
<p>Which settings are required will depend on the type of repository you are deploying to. As of the first release, only SCP deployments and file deployments are supported by default, so only the following SCP configuration is needed:</p>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-encryption.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-encryption.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-encryption.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Password Encryption</title>
+ <title>Maven – Password Encryption</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -15,7 +15,7 @@
<meta name="author" content="Oleg Gusakov
Robert Scholte" />
<meta name="Date-Creation-yyyymmdd" content="20140323" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -45,7 +45,7 @@ Robert Scholte" />
Password Encryption
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -345,7 +345,7 @@ Robert Scholte" />
<div class="section">
<h3><a name="Tips">Tips</a></h3>
<div class="section">
-<h4>Escaping curly-brace literals in your password <i>(Since: Maven 2.2.0)</i><a name="Escaping_curly-brace_literals_in_your_password_Since:_Maven_2.2.0"></a></h4>
+<h4><a name="Escaping_curly-brace_literals_in_your_password_Since:_Maven_2.2.0"></a>Escaping curly-brace literals in your password <i>(Since: Maven 2.2.0)</i></h4>
<p>At times, you might find that your password (or the encrypted form of it) may actually contain '{' or '}' as a literal value. If you added such a password as-is to your settings.xml file, you would find that Maven does strange things with it. Specifically, Maven will treat all the characters preceding the '{' literal, and all the characters after the '}' literal, as comments. Obviously, this is not the behavior you want in such a situation. What you really need is a way of <b>escaping</b> the curly-brace literals in your password.</p>
<p>Starting in Maven 2.2.0, you can do just this, with the widely used '\' escape character. If your password looks like this:</p>
<div class="source">
@@ -354,14 +354,14 @@ Robert Scholte" />
<div class="source">
<pre>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+\{EF1iFQyJQ=}</pre></div></div>
<div class="section">
-<h4>Password Security<a name="Password_Security"></a></h4>
+<h4><a name="Password_Security"></a>Password Security</h4>
<p>Editing <tt>settings.xml</tt> and running the above commands can still leave your password stored locally in plaintext. You may want to check the following locations:</p>
<ul>
<li>Shell history (e.g. by running <tt>history</tt>). You may want to clear your history after encrypting the above passwords</li>
<li>Editor caches (e.g. <tt>~/.viminfo</tt>)</li></ul>
<p>Also note that the encrypted passwords can be decrypted by someone that has the master password and settings security file. Keep this file secure (or stored separately) if you expect the possibility that the <tt>settings.xml</tt> file may be retrieved.</p></div>
<div class="section">
-<h4>Password Escaping on different platforms<a name="Password_Escaping_on_different_platforms"></a></h4>
+<h4><a name="Password_Escaping_on_different_platforms"></a>Password Escaping on different platforms</h4>
<p>On some platforms it might be neccessary to quote your password based on the content of your password in particular having special characters like <tt>%</tt>, <tt>!</tt>, <tt>$</tt> etc. in there. For example on Windows you have to be carefull about things like the following:</p>
<p>The following example will not work on Windows:</p>
<div class="source">
Modified: websites/staging/maven/trunk/content/guides/mini/guide-generating-sources.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-generating-sources.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-generating-sources.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to generating Sources</title>
+ <title>Maven – Guide to generating Sources</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Jason van Zyl" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Guide to generating Sources
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -241,7 +241,7 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Guide to generating sources<a name="Guide_to_generating_sources"></a></h2>
+<h2><a name="Guide_to_generating_sources"></a>Guide to generating sources</h2>
<p>Let's run though a short example to try and help. To generate sources you must first have a plugin that participates in the <tt>generate-sources</tt> phase like the Antlr plugin:</p>
<div class="source">
<pre>Error during retrieving content skip as ignoreDownloadError activated.</pre></div>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-http-settings.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-http-settings.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-http-settings.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Advanced HTTP Wagon Configuration</title>
+ <title>Maven – Guide to Advanced HTTP Wagon Configuration</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -14,7 +14,7 @@
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="John Casey" />
<meta name="Date-Creation-yyyymmdd" content="20111212" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -44,7 +44,7 @@
Guide to Advanced HTTP Wagon Configuration
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -242,7 +242,7 @@
<div id="bodyColumn">
<div id="contentBox">
<!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements. See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership. The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License. You may obtain a copy of the License at --><!-- --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!-- --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied. See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><!-- NOTE: For help with the syntax of this file, see: --><!-- http://maven.apache.org/doxia/references/apt-
format.html --><div class="section">
-<h2>Advanced Configuration of the HttpClient HTTP Wagon<a name="Advanced_Configuration_of_the_HttpClient_HTTP_Wagon"></a></h2>
+<h2><a name="Advanced_Configuration_of_the_HttpClient_HTTP_Wagon"></a>Advanced Configuration of the HttpClient HTTP Wagon</h2>
<ul>
<li><a href="#Advanced_Configuration_of_the_HttpClient_HTTP_Wagon">Advanced Configuration of the HttpClient HTTP Wagon</a>
<ul>
@@ -267,16 +267,16 @@
<li><a href="#Read_time_out">Read time out</a></li></ul></li>
<li><a href="#Resources">Resources</a></li></ul></li></ul>
<div class="section">
-<h3>Notice on Maven Versioning and Availability<a name="Notice_on_Maven_Versioning_and_Availability"></a></h3>
+<h3><a name="Notice_on_Maven_Versioning_and_Availability"></a>Notice on Maven Versioning and Availability</h3>
<div class="section">
-<h4>Maven 2.2.0<a name="Maven_2.2.0"></a></h4>
+<h4><a name="Maven_2.2.0"></a>Maven 2.2.0</h4>
<p>Starting in <b>Maven 2.2.0</b>, the HttpClient wagon was the implementation in use. The remainder of this document deals specifically with the differences between the HttpClient- and Sun-based HTTP wagons.</p></div>
<div class="section">
-<h4>Maven 2.2.1<a name="Maven_2.2.1"></a></h4>
+<h4><a name="Maven_2.2.1"></a>Maven 2.2.1</h4>
<p>Due to several critical issues introduced by the HttpClient-based HTTP wagon, <b>Maven 2.2.1</b> reverted back to the Sun implementation (a.k.a. 'lightweight') of the HTTP wagon as the default for HTTP/HTTPS transfers. The issues with the HttpClient-based wagon were mainly related to checksums, transfer timeouts, and NTLM proxies, and served as the primary cause for the release of <b>2.2.1</b> in the first place.</p>
<p><b>However</b>, starting in <b>Maven 2.2.1</b> you have a choice: you can use the default wagon implementation for a given protocol, or you can select an alternative wagon <tt>provider</tt> you'd like to use on a per-protocol basis. For more information, see the <a href="./guide-wagon-providers.html">Guide to Wagon Providers</a> [3].</p></div>
<div class="section">
-<h4>Maven 3.0.4<a name="Maven_3.0.4"></a></h4>
+<h4><a name="Maven_3.0.4"></a>Maven 3.0.4</h4>
<p>With 3.0.4, the default wagon http(s) is now the HttpClient based on <a class="externalLink" href="http://hc.apache.org/httpcomponents-client-ga">Apache Http Client 4.1.2</a>. There is now a http connection pooling to prevent reopening http(s) to remote server for each requests. This pool feature is configurable with some parameters [4].</p>
<p>This new defaut wagon comes with some default configuration:</p>
<ul>
@@ -284,10 +284,10 @@
<li>readTimeout: default to 1800000ms (~30 minutes) (see section <tt>Read time out</tt> below)</li>
<li>default Preemptive Authentication only with PUT (GET doesn't use anymore default Preemptive Authentication)</li></ul></div></div>
<div class="section">
-<h3>Introduction<a name="Introduction"></a></h3>
+<h3><a name="Introduction"></a>Introduction</h3>
<p>Using the HttpClient-based HTTP wagon, you have a lot more control over the configuration used to access HTTP-based Maven repositories. For starters, you have fine-grained control over what HTTP headers are used when resolving artifacts. In addition, you can also configure a wide range of parameters to control the behavior of HttpClient itself. Best of all, you have the ability to control these headers and parameters for all requests, or individual request types (Maven issues GET, HEAD, and PUT requests for different parts of the artifact-management subsystem).</p></div>
<div class="section">
-<h3>The Basics<a name="The_Basics"></a></h3>
+<h3><a name="The_Basics"></a>The Basics</h3>
<p>Without any special configuration, Maven's HTTP wagon will use some default HTTP headers and client parameters when managing artifacts. The default headers are:</p>
<div class="source">
<pre>Cache-control: no-cache
@@ -316,7 +316,7 @@ problems with HTTP servers and proxies t
<p>Another option to avoid this double transfer is what's known as preemptive authentication, which involves sending the authentication headers along with the original PUT request. However, there are a few potential issues with this approach. For one thing, in the event you have an unused <tt><server></tt> entry that specifies an invalid username/password combination, some servers may respond with a <tt>401 Unauthorized</tt> even if the server doesn't actually require any authentication for the request. In addition, blindly sending authentication credentials with every request regardless of whether the server has made a challenge can result in a security hole, since the server may not make provisions to secure credentials for paths that don't require authentication.</p>
<p>We'll discuss preemptive authentication in another example, below.</p></div>
<div class="section">
-<h3>Configuring GET, HEAD, PUT, or All of the Above<a name="Configuring_GET_HEAD_PUT_or_All_of_the_Above"></a></h3>
+<h3><a name="Configuring_GET_HEAD_PUT_or_All_of_the_Above"></a>Configuring GET, HEAD, PUT, or All of the Above</h3>
<p>In all of the examples below, it's important to understand that we can configure the HTTP settings for all requests made to a given server, or for only one method. To configure all methods for a server, you'd use the following section of the <tt>settings.xml</tt> file:</p>
<div class="source">
<pre><settings>
@@ -353,7 +353,7 @@ problems with HTTP servers and proxies t
</settings></pre></div>
<p>For clarity, the other two sections are <tt><get></tt> for GET requests, and <tt><head></tt> for HEAD requests. I know that's going to be hard to remember...</p></div>
<div class="section">
-<h3>Taking Control of Your HTTP Headers<a name="Taking_Control_of_Your_HTTP_Headers"></a></h3>
+<h3><a name="Taking_Control_of_Your_HTTP_Headers"></a>Taking Control of Your HTTP Headers</h3>
<p>As you may have noticed above, the default HTTP headers do have the potential to cause problems. For instance, some websites set the encoding for downloading GZipped files as <tt>gzip</tt>, in spite of the fact that the HTTP request itself isn't being sent using GZip compression. If the client is using the <tt>Accept-Encoding: gzip</tt> header, this can result in the client itself decompressing the GZipped file <i>during the transfer</i> and writing the decompressed file to the local disk with the original filename. This can be misleading to say the least, and can use up an inordinate amount of disk space on the local computer.</p>
<p>To turn off this default behavior, we'll simply disable the default headers. Then, we'll need to respecify the other headers that we are still interested in, like this:</p>
<div class="source">
@@ -397,10 +397,10 @@ problems with HTTP servers and proxies t
[...]
</settings></pre></div></div>
<div class="section">
-<h3>Fine-Tuning HttpClient Parameters<a name="Fine-Tuning_HttpClient_Parameters"></a></h3>
+<h3><a name="Fine-Tuning_HttpClient_Parameters"></a>Fine-Tuning HttpClient Parameters</h3>
<p>Going beyond the power of HTTP request parameters, HttpClient provides a host of other configuration options. In most cases, you won't need to customize these. But in case you do, Maven provides access to specify your own fine-grained configuration for HttpClient. Again, you can specify these parameter customizations per-method (HEAD, GET, or PUT), or for all methods of interacting with a given server. For a complete list of supported parameters, see the link[2] in Resources section below.</p>
<div class="section">
-<h4>Non-String Parameter Values<a name="Non-String_Parameter_Values"></a></h4>
+<h4><a name="Non-String_Parameter_Values"></a>Non-String Parameter Values</h4>
<p>Many of the configuration parameters for HttpClient have simple string values; however, there are important exceptions to this. In some cases, you may need to specify boolean, integer, or long values. In others, you may even need to specify a collection of string values. You can specify these using a simple formatting syntax, as follows:</p>
<ol style="list-style-type: decimal">
<li><b>booleans:</b> <tt>%b,<value></tt></li>
@@ -416,7 +416,7 @@ problems with HTTP servers and proxies t
...</pre></div></li></ol>
<p>As you may have noticed, this syntax is similar to the format-and-data strategy used by functions like <tt>sprintf()</tt> in many languages. The syntax has been chosen with this similarity in mind, to make it a little more intuitive to use.</p></div>
<div class="section">
-<h4>Example: Using Preemptive Authentication<a name="Example:_Using_Preemptive_Authentication"></a></h4>
+<h4><a name="Example:_Using_Preemptive_Authentication"></a>Example: Using Preemptive Authentication</h4>
<p>Using the above syntax, we can configure preemptive authentication for PUT requests using the boolean HttpClient parameter <tt>http.authentication.preemptive</tt>, like this:</p>
<div class="source">
<pre><settings>
@@ -439,7 +439,7 @@ problems with HTTP servers and proxies t
</servers>
</settings></pre></div></div>
<div class="section">
-<h4>Ignoring Cookies<a name="Ignoring_Cookies"></a></h4>
+<h4><a name="Ignoring_Cookies"></a>Ignoring Cookies</h4>
<p>Like the example above, telling the HttpClient to ignore cookies for all methods of request is a simple matter of configuring the <tt>http.protocol.cookie-policy</tt> parameter (it uses a regular string value, so no special syntax is required):</p>
<div class="source">
<pre><settings>
@@ -463,10 +463,10 @@ problems with HTTP servers and proxies t
</settings></pre></div>
<p>The configuration above can be useful in cases where the repository is using cookies - like the session cookies that are often mistakenly turned on or left on in appservers - alongside HTTP redirection. In these cases, it becomes far more likely that the cookie issued by the appserver will use a <tt>Path</tt> that is inconsistent with the one used by the client to access the server. If you have this problem, and know that you don't need to use this session cookie, you can ignore cookies from this server with the above configuration.</p></div></div>
<div class="section">
-<h3>Support for General-Wagon Configuration Standards<a name="Support_for_General-Wagon_Configuration_Standards"></a></h3>
+<h3><a name="Support_for_General-Wagon_Configuration_Standards"></a>Support for General-Wagon Configuration Standards</h3>
<p>It should be noted that configuration options previously available in the HttpClient-driven HTTP wagon are still supported in addition to this new, fine-grained approach. These include the configuration of HTTP headers and connection timeouts. Let's examine each of these briefly:</p>
<div class="section">
-<h4>HTTP Headers<a name="HTTP_Headers"></a></h4>
+<h4><a name="HTTP_Headers"></a>HTTP Headers</h4>
<p>In all HTTP Wagon implementations, you can add your own HTTP headers like this:</p>
<div class="source">
<pre><settings>
@@ -486,7 +486,7 @@ problems with HTTP servers and proxies t
</settings></pre></div>
<p>It's important to understand that the above approach doesn't allow you to turn off all of the default HTTP headers; nor does it allow you to specify headers on a per-method basis. However, this configuration remains available in both the lightweight and httpclient-based Wagon implementations.</p></div>
<div class="section">
-<h4>Connection Timeouts<a name="Connection_Timeouts"></a></h4>
+<h4><a name="Connection_Timeouts"></a>Connection Timeouts</h4>
<p>All wagon implementations that extend the <tt>AbstractWagon</tt> class, including those for SCP, HTTP, FTP, and more, allow the configuration of a connection timeout, to allow the user to tell Maven how long to wait before giving up on a connection that has not responded. This option is preserved in the HttpClient-based wagon, but this wagon also provides a fine-grained alternative configuration that can allow you to specify timeouts per-method for a given server. The old configuration option - which is still supported - looks like this:</p>
<div class="source">
<pre><settings>
@@ -517,7 +517,7 @@ problems with HTTP servers and proxies t
</settings></pre></div>
<p>If all you need is a per-server timeout configuration, you still have the option to use the old <tt><timeout></tt> parameter. If you need to separate timeout preferences according to HTTP method, you can use one more like that specified directly above.</p></div>
<div class="section">
-<h4>Read time out<a name="Read_time_out"></a></h4>
+<h4><a name="Read_time_out"></a>Read time out</h4>
<p>With Wagon 2.0 and Apache Maven 3.0.4, a default timeout of 30 minutes comes by default. If you want to change this value, you can add the following setup in your settings:</p>
<div class="source">
<pre><settings>
@@ -535,7 +535,7 @@ problems with HTTP servers and proxies t
</servers>
</settings></pre></div></div></div>
<div class="section">
-<h3>Resources<a name="Resources"></a></h3>
+<h3><a name="Resources"></a>Resources</h3>
<ol style="list-style-type: decimal">
<li><a class="externalLink" href="http://hc.apache.org/httpclient-3.x/">HttpClient website</a></li>
<li><a class="externalLink" href="http://hc.apache.org/httpclient-3.x/preference-api.html">HttpClient preference architecture and configuration guide</a></li>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-ide-eclipse.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-ide-eclipse.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-ide-eclipse.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to using Eclipse with Maven 2.x</title>
+ <title>Maven – Guide to using Eclipse with Maven 2.x</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -14,7 +14,7 @@
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Bernd Mau, mau@hhla.de" />
<meta name="Date-Creation-yyyymmdd" content="20100121" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -44,7 +44,7 @@
Guide to using Eclipse with Maven 2.x
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -242,7 +242,7 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Guide to using Eclipse with Maven 2.x<a name="Guide_to_using_Eclipse_with_Maven_2.x"></a></h2>
+<h2><a name="Guide_to_using_Eclipse_with_Maven_2.x"></a>Guide to using Eclipse with Maven 2.x</h2>
<p>This mini guide explains howto use Maven 2 in Eclipse IDE.</p>
<ul>
<li><a href="#Maven_2_repository">Maven 2 repository</a></li>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-ide-idea.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-ide-idea.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-ide-idea.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to using IDEA with Maven 2.x</title>
+ <title>Maven – Guide to using IDEA with Maven 2.x</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Jason van Zyl" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Guide to using IDEA with Maven 2.x
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -241,7 +241,7 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Guide to using IDEA with Maven 2.x <a name="Guide_to_using_IDEA_with_Maven_2.x"></a></h2>
+<h2><a name="Guide_to_using_IDEA_with_Maven_2.x"></a>Guide to using IDEA with Maven 2.x </h2>
<p>To generate the IDEA project files from your POM you execute the following command:</p>
<div class="source">
<pre>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-ide-netbeans/guide-ide-netbeans.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-ide-netbeans/guide-ide-netbeans.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-ide-netbeans/guide-ide-netbeans.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Using Maven 2 in NetBeans 4.0 (4.1 and 5.0)</title>
+ <title>Maven – Guide to Using Maven 2 in NetBeans 4.0 (4.1 and 5.0)</title>
<style type="text/css" media="all">
@import url("../../../css/maven-base.css");
@import url("../../../css/maven-theme.css");
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Raphaël Piéroni" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Guide to Using Maven 2 in NetBeans 4.0 (4.1 and 5.0)
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -241,7 +241,7 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Using Maven 2 in NetBeans 4.0 (4.1 and 5.0)<a name="Using_Maven_2_in_NetBeans_4.0_4.1_and_5.0"></a></h2>
+<h2><a name="Using_Maven_2_in_NetBeans_4.0_4.1_and_5.0"></a>Using Maven 2 in NetBeans 4.0 (4.1 and 5.0)</h2>
<p>This mini guide explain by examples how to use Maven 2 in NetBeans IDE.</p>
<p>To use Maven 2 in NetBeans you have to follow these steps:</p>
<ul>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-m1-m2.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-m1-m2.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-m1-m2.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Moving From Maven 1.x to Maven 2.x</title>
+ <title>Maven – Guide to Moving From Maven 1.x to Maven 2.x</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Jay H. Hartley" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Guide to Moving From Maven 1.x to Maven 2.x
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -241,10 +241,10 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Guide to Moving from Maven 1.x to Maven 2.x<a name="Guide_to_Moving_from_Maven_1.x_to_Maven_2.x"></a></h2>
+<h2><a name="Guide_to_Moving_from_Maven_1.x_to_Maven_2.x"></a>Guide to Moving from Maven 1.x to Maven 2.x</h2>
<p>This document is intended to be continuously updated from the mail list archives. For an only slightly out-of-date reference with concrete examples, check out Vincent Massol's <a class="externalLink" href="http://blogs.codehaus.org/people/vmassol/archives/001170_javazone_2005.html">JavaZone2005 presentation</a>.</p>
<div class="section">
-<h3>Parallel Builds<a name="Parallel_Builds"></a></h3>
+<h3><a name="Parallel_Builds"></a>Parallel Builds</h3>
<p>It is possible to establish parallel Maven builds, one using the old M1 settings, and a second using M2. The Maven 2 configuration file names and uses have been modified, so the two builds should not conflict.</p>
<p>A Maven 1.x build is configured with the following files:</p>
<ul>
@@ -256,7 +256,7 @@
<li>[pom.xml] POM definition</li>
<li>[settings.xml] local configuration</li></ul></div>
<div class="section">
-<h3>Migrating the POM<a name="Migrating_the_POM"></a></h3>
+<h3><a name="Migrating_the_POM"></a>Migrating the POM</h3>
<p>The Project Object Model (POM) has moved from the <tt>project.xml</tt> file to <tt>pom.xml</tt>. The XML schema has also changed, from <a class="externalLink" href="http://maven.apache.org/xsd/maven-v3_0_0.xsd">Version 3</a> to <a class="externalLink" href="http://maven.apache.org/xsd/maven-4.0.0.xsd">Version 4</a>.</p>
<p>The new POM is nominally a superset of the old, so the first step in creating a <tt>pom.xml</tt> is to copy over <tt>project.xml</tt>. Then start tweaking. There are several new elements that can be added to a POM, but all are optional so should not cause a problem with an initial build.</p>
<p>If you want some help converting your <tt>project.xml</tt> into a <tt>pom.xml</tt> you can use the <a class="externalLink" href="http://maven.apache.org/plugins/maven-one-plugin/">maven-one-plugin</a>. If you run the following command, it will convert your <tt>project.xml</tt> into a <tt>pom.xml</tt>:</p>
@@ -298,28 +298,28 @@
</project></pre></div>
<p>For more details, check out the <a href="../introduction/introduction-to-the-pom.html">POM Guide</a>.</p></div>
<div class="section">
-<h3>build.properties and project.properties<a name="build.properties_and_project.properties"></a></h3>
+<h3><a name="build.properties_and_project.properties"></a>build.properties and project.properties</h3>
<p>These files have been replaced with <a href="../../settings.html">settings.xml</a>. Like with the POM, you can establish a parallel build environment, so the m1 build never breaks while the m2 build is being debugged.</p>
<p>Additional local build customization options can also be created using <a href="../introduction/introduction-to-profiles.html">profiles</a>.</p></div>
<div class="section">
-<h3>What to do with maven.xml?<a name="What_to_do_with_maven.xml"></a></h3>
+<h3><a name="What_to_do_with_maven.xml"></a>What to do with maven.xml?</h3>
<p>See <a href="../../maven1.html#m1-maven-xml">How do I write custom scripts without a maven.xml file?</a> for an explanation of why maven.xml was discarded, and <a href="../introduction/introduction-to-plugins.html">Introduction to Maven 2.0 Plugin Development</a> for a guide to writing your own plug-ins.</p></div>
<div class="section">
-<h3>Directory Structure<a name="Directory_Structure"></a></h3>
+<h3><a name="Directory_Structure"></a>Directory Structure</h3>
<p>The POM allows customization of the directory structure in both Maven 1 and Maven 2 using the <tt><build></tt> tag. For simplicity, it would be ideal to move source to the <a href="../introduction/introduction-to-the-standard-directory-layout.html">Maven 2 default structure</a>, but it is not required. You can begin by customizing the directories in Maven 2, then when satisfied that both build paths are working, move to the Maven 2 structure and customize the settings in Maven 1.</p></div>
<div class="section">
-<h3>Migrating Plug-ins<a name="Migrating_Plug-ins"></a></h3>
+<h3><a name="Migrating_Plug-ins"></a>Migrating Plug-ins</h3>
<p>The main conceptual change in plugins and their use has to do with the concept of a build cycle in Maven 2. Instead of using <tt>preGoal</tt> and <tt>postGoal</tt> tags in <tt>maven.xml</tt> to tie plugin goals into the build process, the goals of a plugin are associated with the pre-defined stages of the build cycle. See the <a href="../introduction/introduction-to-the-lifecycle.html">Introduction to the Build Lifecycle</a> for more on how plugins relate.</p>
<div class="section">
-<h4>Re-use Ant Tasks<a name="Re-use_Ant_Tasks"></a></h4>
+<h4><a name="Re-use_Ant_Tasks"></a>Re-use Ant Tasks</h4>
<p>See the <a href="../../general.html#using-ant-tasks">Ant Script FAQ</a>.</p></div>
<div class="section">
-<h4>Replace scripts with Mojos<a name="Replace_scripts_with_Mojos"></a></h4>
+<h4><a name="Replace_scripts_with_Mojos"></a>Replace scripts with Mojos</h4>
<p>The new plugin architecture does not specify a specific language implementation, so Jelly scripts and other such artifacts should be re-usable with wrappers. It is recommended that you look into moving to <a href="../plugin/guide-java-plugin-development.html">Mojos</a>.</p></div>
<div class="section">
-<h4>Utilize built-in Maven 2 capabilities<a name="Utilize_built-in_Maven_2_capabilities"></a></h4>
+<h4><a name="Utilize_built-in_Maven_2_capabilities"></a>Utilize built-in Maven 2 capabilities</h4>
<div class="section">
-<h5>Resource filtering to inject POM variables into application<a name="Resource_filtering_to_inject_POM_variables_into_application"></a></h5>
+<h5><a name="Resource_filtering_to_inject_POM_variables_into_application"></a>Resource filtering to inject POM variables into application</h5>
<p>You can turn on <a href="../getting-started/index.html#How_do_I_filter_resource_files">resource filtering</a> in your POM. Tokens of the form <tt>${pom.variable}</tt> in resource files will be replaced with the corresponding POM property.</p>
<div class="source">
<pre><project>
@@ -334,13 +334,13 @@
</build>
</project></pre></div></div>
<div class="section">
-<h5>Multiproject Builds<a name="Multiproject_Builds"></a></h5>
+<h5><a name="Multiproject_Builds"></a>Multiproject Builds</h5>
<p>The old reactor+multiproject plugin combination was established more as an afterthought of the core development. In Maven 2, multiproject support is included in the core, so any scripts required in the past to work around problems with the multiproject plugin should be unnecessary.</p></div></div></div>
<div class="section">
-<h3>Migrating repositories<a name="Migrating_repositories"></a></h3>
+<h3><a name="Migrating_repositories"></a>Migrating repositories</h3>
<p>Every four hours the Maven 1.x repository is converted over to a Maven 2.x repository and we plan to release a plug-in based on our conversion tool but currently.</p></div>
<div class="section">
-<h3>Related links<a name="Related_links"></a></h3>
+<h3><a name="Related_links"></a>Related links</h3>
<ul>
<li><a class="externalLink" href="http://maven.apache.org/plugins/maven-one-plugin/">Maven 2 One Plugin</a></li>
<li><a class="externalLink" href="https://svn.apache.org/repos/asf/maven/sandbox/trunk/other/m1-m2/maven1+project+to+maven2+pom.xsl">XSLT</a> from <a class="externalLink" href="http://jira.codehaus.org/browse/MNG-2337">MNG-2337</a></li>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-manifest.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-manifest.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-manifest.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Working with Manifests</title>
+ <title>Maven – Guide to Working with Manifests</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -15,7 +15,7 @@
<meta name="author" content="Jason van Zyl
Dennis Lundberg" />
<meta name="Date-Creation-yyyymmdd" content="20100819" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -45,7 +45,7 @@ Dennis Lundberg" />
Guide to Working with Manifests
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -243,7 +243,7 @@ Dennis Lundberg" />
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Guide to Working with Manifests<a name="Guide_to_Working_with_Manifests"></a></h2>
+<h2><a name="Guide_to_Working_with_Manifests"></a>Guide to Working with Manifests</h2>
<p>In order to modify the manifest of the archive produced by the packaging plug-ins you need to create a configuration for it. The definitive guide for this is <a href="/shared/maven-archiver/index.html">the site for the Maven Archiver shared component</a>. This component is used by all our packaging plugins.</p><!-- suggestion by jorg --><!-- it would be nice if the Specification-Version could be easily generated to be major.minor of pom.currentVersion i.e. that --><!-- --><!-- 1.2 ==> 1.2 --><!-- 1.2.1 ==> 1.2 --><!-- 1.2-SNAPSHOT ==> 1.2 --><!-- for the javaapp-plugin I did something like this in Jelly ... --></div>
</div>
</div>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-maven-classloading.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-maven-classloading.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-maven-classloading.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Maven Classloading</title>
+ <title>Maven – Guide to Maven Classloading</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -15,7 +15,7 @@
<meta name="author" content="Jason van Zyl
Anders Kristian Andersen" />
<meta name="Date-Creation-yyyymmdd" content="20081210" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -45,7 +45,7 @@ Anders Kristian Andersen" />
Guide to Maven Classloading
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -243,17 +243,17 @@ Anders Kristian Andersen" />
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Guide to Maven Classloading<a name="Guide_to_Maven_Classloading"></a></h2>
+<h2><a name="Guide_to_Maven_Classloading"></a>Guide to Maven Classloading</h2>
<p>This is a description of the classloader hierarchy in Maven 2.0.6+.</p>
<div class="section">
-<h3>Overview<a name="Overview"></a></h3>
+<h3><a name="Overview"></a>Overview</h3>
<ul>
<li>System Classloader</li>
<li>Core Classloader</li>
<li>Plugin Classloaders</li>
<li>Custom Classloaders</li></ul></div>
<div class="section">
-<h3>1. <a name="System_Classloader">System Classloader</a><a name="a1._System_Classloader"></a></h3>
+<h3><a name="a1._System_Classloader"></a>1. <a name="System_Classloader">System Classloader</a></h3>
<p>Maven uses the <a class="externalLink" href="http://classworlds.codehaus.org">Classworlds</a> classloading framework with which we create our classloader graph. If you look in your <tt>${maven.home}/boot</tt> directory you will see a single JAR which is the Classworlds JAR we use to boot the classloader graph. The Classworlds JAR is the only element of the Java <tt>CLASSPATH</tt> and Classworlds then builds the other classloaders or realms in Classworlds terminology.</p>
<p>An Ant script like this will show the contents of the system classloader:</p>
<div>
@@ -261,12 +261,12 @@ Anders Kristian Andersen" />
<echo>java.class.path=${java.class.path}</echo>
</target></pre></div></div>
<div class="section">
-<h3>2. <a name="Core_Classloader">Core Classloader</a><a name="a2._Core_Classloader"></a></h3>
+<h3><a name="a2._Core_Classloader"></a>2. <a name="Core_Classloader">Core Classloader</a></h3>
<p>The second classloader down the graph contains the core requirements of Maven. More precisely, the core classloader has the libraries in <tt>${maven.home}/lib</tt>. In general these are just Maven libraries, e.g. instances of</p>
<p><tt><a class="externalLink" href="http://maven.apache.org/ref/current/apidocs/org/apache/maven/project/MavenProject.html">MavenProject</a></tt> belong to this classloader. We hope to further separate these in the future to just be Maven APIs and have the implementations selected at runtime as required by the system.</p>
<p>You can add elements to this classloader by <a class="externalLink" href="http://maven.apache.org/ref/current/maven-model/maven.html#class_extension">extensions</a>. These are loaded into the same place as <tt>${maven.home}/lib</tt> and hence are available to the Maven core and all plugins for the current project and subsequent projects (in future, we plan to remove it from subsequent projects).</p></div>
<div class="section">
-<h3>3. <a name="Plugin_Classloaders">Plugin Classloaders</a><a name="a3._Plugin_Classloaders"></a></h3>
+<h3><a name="a3._Plugin_Classloaders"></a>3. <a name="Plugin_Classloaders">Plugin Classloaders</a></h3>
<p>After that, each plugin has its own classloader that is a child of Maven's core classloader. The classes in this classloader are taken from the dependencies in the plugin's dependency list.</p>
<p>Users can add dependencies to this classloader by adding dependencies to a plugin in the <tt><a class="externalLink" href="http://maven.apache.org/ref/current/maven-model/maven.html#class_plugin">plugins/plugin</a></tt> section of their project <tt>pom.xml</tt>. Here is a sample of adding <tt>ant-nodeps</tt> to the plugin classloader of the Antrun Plugin and hereby enabling the use of additional/optional Ant tasks:</p>
<div>
@@ -287,7 +287,7 @@ Anders Kristian Andersen" />
<p>Please note that the plugin classloader does neither contain the <a class="externalLink" href="http://maven.apache.org/ref/current/maven-model/maven.html#class_dependency">dependencies</a> of the current project nor its build output. Instead, plugins can query the project's compile, runtime and test class path from the <tt><a class="externalLink" href="http://maven.apache.org/ref/current/apidocs/org/apache/maven/project/MavenProject.html">MavenProject</a></tt> in combination with the mojo annotation <tt>requiresDependencyResolution</tt> from the <a class="externalLink" href="http://maven.apache.org/developers/mojo-api-specification.html">Mojo API Specification</a>. For instance, flagging a mojo with <tt>@requiresDependencyResolution runtime</tt> enables it to query the runtime class path of the current project from which it could create further classloaders.</p>
<p>When a build plugin is executed, the thread's context classloader is set to the plugin classloader.</p></div>
<div class="section">
-<h3>4. <a name="Custom_Classloaders">Custom Classloaders</a><a name="a4._Custom_Classloaders"></a></h3>
+<h3><a name="a4._Custom_Classloaders"></a>4. <a name="Custom_Classloaders">Custom Classloaders</a></h3>
<p>Plugins are free to create further classloaders on their discretion. For example, a plugin might want to create a classloader that combines the plugin class path and the project class path.</p>
<p>It is important to understand that the plugin classloader cannot load classes from any of those custom classloaders. Some factory patterns require that. Here you must add the classes to the plugin classloader as shown before.</p></div></div>
</div>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-maven-evangelism.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-maven-evangelism.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-maven-evangelism.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Maven Evangelism</title>
+ <title>Maven – Guide to Maven Evangelism</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Carlos Sanchez" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Guide to Maven Evangelism
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -241,7 +241,7 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Guide to add, improve or fix metadata in the Central Maven 2 repository<a name="Guide_to_add_improve_or_fix_metadata_in_the_Central_Maven_2_repository"></a></h2>
+<h2><a name="Guide_to_add_improve_or_fix_metadata_in_the_Central_Maven_2_repository"></a>Guide to add, improve or fix metadata in the Central Maven 2 repository</h2>
<p>There are artifacts in the repository that don't have POMs. They come from projects with repositories that have been synced into central without extra checks (particularly historical ones that were in Maven 1 format). We know about the problems but can't do anything unless you provide a POM for it or you ask the project in question to add the POM when they add the artifacts.</p>
<p>We don't change dependencies in POMs already in the repository anymore as builds need to be reproducible. Same applies to POMs that don't exist. We can only add a POM with no dependencies, because doing any other way would break previous builds that were using that artifact.</p>
<p>An alternative is to create a new version with the fixes. If the broken artifact is <tt>org.foo/bar/1.0</tt> you can provide a fixed POM,JAR,... under <tt>org.foo/bar/1.0-1</tt> (add a comment to the POM explaining what is being fixed and why). See <a href="./guide-central-repository-upload.html">Maven Repository Upload</a> for the instructions to get this new version in the repository.</p>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-mirror-settings.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-mirror-settings.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-mirror-settings.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Mirror Settings</title>
+ <title>Maven – Guide to Mirror Settings</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -15,7 +15,7 @@
<meta name="author" content="Jason van Zyl
Brian Fox" />
<meta name="Date-Creation-yyyymmdd" content="20080901" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -45,7 +45,7 @@ Brian Fox" />
Guide to Mirror Settings
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -243,7 +243,7 @@ Brian Fox" />
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Using Mirrors for Repositories<a name="Using_Mirrors_for_Repositories"></a></h2>
+<h2><a name="Using_Mirrors_for_Repositories"></a>Using Mirrors for Repositories</h2>
<p>Repositories are declared inside a project, which means that if you have your own custom repositories, those sharing your project easily get the right settings out of the box. However, you may want to use an alternative mirror for a particular repository without changing the project files.</p>
<p>Some reasons to use a mirror are:</p>
<ul>
@@ -269,7 +269,7 @@ Brian Fox" />
<p><b>Note</b>: The official Maven 2 repository is at <tt>http://repo.maven.apache.org/maven2</tt> hosted in the US, or <tt>http://uk.maven.org/maven2</tt> hosted in the UK. </p>
<p>A list of known mirrors is available in the <a class="externalLink" href="http://repo.maven.apache.org/maven2/.meta/repository-metadata.xml">Repository Metadata</a>. These mirrors may not have the same contents and we don't support them in any way.</p></div>
<div class="section">
-<h2>Using A Single Repository<a name="Using_A_Single_Repository"></a></h2>
+<h2><a name="Using_A_Single_Repository"></a>Using A Single Repository</h2>
<p>You can force Maven to use a single repository by having it mirror all repository requests. The repository must contain all of the desired artifacts, or be able to proxy the requests to other repositories. This setting is most useful when using an internal company repository with the Maven Repository Manager to proxy external requests.</p>
<p>To achieve this, set <tt>mirrorOf</tt> to <tt>*</tt>.</p>
<p><b>Note:</b> This feature is only available in Maven 2.0.5+.</p>
@@ -287,7 +287,7 @@ Brian Fox" />
...
</settings></pre></div></div>
<div class="section">
-<h2>Advanced Mirror Specification<a name="Advanced_Mirror_Specification"></a></h2>
+<h2><a name="Advanced_Mirror_Specification"></a>Advanced Mirror Specification</h2>
<p>A single mirror can handle multiple repositories when used in conjunction with a repository manager.</p>
<p>The syntax as of Maven 2.0.9:</p>
<ul>
@@ -324,7 +324,7 @@ Brian Fox" />
...
</settings></pre></div></div>
<div class="section">
-<h2>Creating Your Own Mirror<a name="Creating_Your_Own_Mirror"></a></h2>
+<h2><a name="Creating_Your_Own_Mirror"></a>Creating Your Own Mirror</h2>
<p>The central repository is over 180 GB and growing. To save us bandwidth and you time, mirroring the entire central repository is not allowed. (Doing so will get you automatically banned) Instead, we suggest you setup a <a href="../../repository-management.html">repository manager</a> as a proxy.</p>
<p>If you really want to become an official mirror, contact us at <a class="externalLink" href="https://issues.sonatype.org/browse/MVNCENTRAL">MVNCENTRAL</a> with your location and we'll work to get you setup.</p></div>
</div>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-multiple-modules.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-multiple-modules.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-multiple-modules.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Working with Multiple Modules</title>
+ <title>Maven – Guide to Working with Multiple Modules</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Brett Porter" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Guide to Working with Multiple Modules
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -241,17 +241,17 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Guide to Working with Multiple Modules<a name="Guide_to_Working_with_Multiple_Modules"></a></h2>
+<h2><a name="Guide_to_Working_with_Multiple_Modules"></a>Guide to Working with Multiple Modules</h2>
<p>As seen in the introduction to the POM, Maven supports project aggregation in addition to project inheritance. This section outlines how Maven processes projects with multiple modules, and how you can work with them more effectively.</p>
<div class="section">
-<h3>The Reactor<a name="The_Reactor"></a></h3>
+<h3><a name="The_Reactor"></a>The Reactor</h3>
<p>The mechanism in Maven that handles multi-module projects is referred to as the <i>reactor</i>. This part of the Maven core does the following:</p>
<ul>
<li>Collects all the available modules to build</li>
<li>Sorts the projects into the correct build order</li>
<li>Builds the selected projects in order</li></ul>
<div class="section">
-<h4>Reactor Sorting<a name="Reactor_Sorting"></a></h4>
+<h4><a name="Reactor_Sorting"></a>Reactor Sorting</h4>
<p>Because modules within a multi-module build can depend on each other, it is important that The reactor sorts all the projects in a way that guarantees any project is built before it is required.</p>
<p>The following relationships are honoured when sorting projects:</p>
<ul>
@@ -262,7 +262,7 @@
<li>the order declared in the <tt><modules></tt> element (if no other rule applies)</li></ul>
<p>Note that only "instantiated" references are used - <tt>dependencyManagement</tt> and <tt>pluginManagement</tt> elements will not cause a change to the reactor sort order</p></div>
<div class="section">
-<h4>Command Line Options<a name="Command_Line_Options"></a></h4>
+<h4><a name="Command_Line_Options"></a>Command Line Options</h4>
<p>No special configuration is required to take advantage of the reactor, however it is possible to customize its behavior.</p>
<p>The following command line switches are available:</p>
<ul>
@@ -275,10 +275,10 @@
<li><tt>--non-recursive</tt> - do not use a reactor build, even if the current project declares modules and just build the project in the current directory</li></ul>
<p>Refer to the Maven command line interface reference for more information on these switches.</p></div>
<div class="section">
-<h4>The Reactor Plugin<a name="The_Reactor_Plugin"></a></h4>
+<h4><a name="The_Reactor_Plugin"></a>The Reactor Plugin</h4>
<p>For versions of Maven prior to Maven 2.1, or for additional capabilities with the reactor such as building only the modules with SCM changes, the Reactor plugin can be used to further customize the execution of the projects. For information on how to use this, refer to the <a href="/plugins/maven-reactor-plugin/index.html"> Reactor Plugin documentation</a>.</p></div></div>
<div class="section">
-<h3>More information<a name="More_information"></a></h3>
+<h3><a name="More_information"></a>More information</h3>
<ul>
<li><a class="externalLink" href="http://www.sonatype.com/books/mvnex-book/reference/multimodule.html"> Chapter 8. A Multi-module Project (Maven by Example)</a></li></ul></div></div>
</div>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-multiple-repositories.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-multiple-repositories.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-multiple-repositories.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to using Multiple Repositories</title>
+ <title>Maven – Guide to using Multiple Repositories</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Jason van Zyl" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Guide to using Multiple Repositories
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -241,7 +241,7 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Setting up Multiple Repositories<a name="Setting_up_Multiple_Repositories"></a></h2>
+<h2><a name="Setting_up_Multiple_Repositories"></a>Setting up Multiple Repositories</h2>
<p>There are two different ways that you can specify the use of multiple repositories. The first way is to specify in a POM which repositories you want to use:</p>
<div class="source">
<pre>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-naming-conventions.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-naming-conventions.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-naming-conventions.html Fri Jul 11 05:10:35 2014
@@ -1,11 +1,11 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- | Generated by Apache Maven Doxia at 2014-07-01
+ | Generated by Apache Maven Doxia at 2014-07-11
| Rendered using Apache Maven Stylus Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <title>Maven - Guide to Naming Conventions</title>
+ <title>Maven – Guide to Naming Conventions</title>
<style type="text/css" media="all">
@import url("../../css/maven-base.css");
@import url("../../css/maven-theme.css");
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Carlos Sanchez" />
- <meta name="Date-Revision-yyyymmdd" content="20140701" />
+ <meta name="Date-Revision-yyyymmdd" content="20140711" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
@@ -43,7 +43,7 @@
Guide to Naming Conventions
</div>
<div class="xright">
- Last Published: 2014-07-01
+ Last Published: 2014-07-11
</div>
<div class="clear">
<hr/>
@@ -241,7 +241,7 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section">
-<h2>Guide to naming conventions on groupId, artifactId and version<a name="Guide_to_naming_conventions_on_groupId_artifactId_and_version"></a></h2>
+<h2><a name="Guide_to_naming_conventions_on_groupId_artifactId_and_version"></a>Guide to naming conventions on groupId, artifactId and version</h2>
<ul>
<li><b>groupId</b> will identify your project uniquely across all projects, so we need to enforce a naming schema. It has to follow the package name rules, what means that has to be at least as a domain name you control, and you can create as many subgroups as you want. Look at <a class="externalLink" href="http://java.sun.com/docs/books/jls/third_edition/html/packages.html#7.7"> More information about package names</a>.
<p>eg. <tt>org.apache.maven</tt>, <tt>org.apache.commons</tt></p>