Author: buildbot
Date: Wed Jan 13 19:39:36 2016
New Revision: 977613
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/guides/getting-started/index.html
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jan 13 19:39:36 2016
@@ -1 +1 @@
-1724472
+1724485
Modified: websites/staging/maven/trunk/content/guides/getting-started/index.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/getting-started/index.html
(original)
+++ websites/staging/maven/trunk/content/guides/getting-started/index.html Wed
Jan 13 19:39:36 2016
@@ -497,7 +497,7 @@ Vincent Siveton" />
<li><a
href="./index.html#How_do_I_compile_my_test_sources_and_run_my_unit_tests">How
do I compile my test sources and run my unit tests?</a></li>
<li><a
href="./index.html#How_do_I_create_a_JAR_and_install_it_in_my_local_repository">How
do I create a JAR and install it in my local repository?</a></li>
<li><a href="./index.html#What_is_a_SNAPSHOT_version">What is a SNAPSHOT
version?</a></li>
-<li><a href="./index.html#How_do_I_use_plug-ins">How do I use
plug-ins?</a></li>
+<li><a href="./index.html#How_do_I_use_plugins">How do I use plugins?</a></li>
<li><a href="./index.html#How_do_I_add_resources_to_my_JAR">How do I add
resources to my JAR?</a></li>
<li><a href="./index.html#How_do_I_filter_resource_files">How do I filter
resource files?</a></li>
<li><a href="./index.html#How_do_I_use_external_dependencies">How do I use
external dependencies?</a></li>
@@ -558,7 +558,7 @@ Vincent Siveton" />
<ul>
<li><b>project</b> This is the top-level element in all Maven pom.xml
files.</li>
<li><b>modelVersion</b> This element indicates what version of the object
model this POM is using. The version of the model itself changes very
infrequently but it is mandatory in order to ensure stability of use if and
when the Maven developers deem it necessary to change the model.</li>
-<li><b>groupId</b> This element indicates the unique identifier of the
organization or group that created the project. The groupId is one of the key
identifiers of a project and is typically based on the fully qualified domain
name of your organization. For example <tt>org.apache.maven.plugins</tt> is the
designated groupId for all Maven plug-ins.</li>
+<li><b>groupId</b> This element indicates the unique identifier of the
organization or group that created the project. The groupId is one of the key
identifiers of a project and is typically based on the fully qualified domain
name of your organization. For example <tt>org.apache.maven.plugins</tt> is the
designated groupId for all Maven plugins.</li>
<li><b>artifactId</b> This element indicates the unique base name of the
primary artifact being generated by this project. The primary artifact for a
project is typically a JAR file. Secondary artifacts like source bundles also
use the artifactId as part of their final name. A typical artifact produced by
Maven would have the form <artifactId>-<version>.<extension>
(for example, <tt>myapp-1.0.jar</tt>).</li>
<li><b>packaging</b> This element indicates the package type to be used by
this artifact (e.g. JAR, WAR, EAR, etc.). This not only means if the artifact
produced is JAR, WAR, or EAR but can also indicate a specific lifecycle to use
as part of the build process. (The lifecycle is a topic we will deal with
further on in the guide. For now, just keep in mind that the indicated
packaging of a project can play a part in customizing the build lifecycle.) The
default value for the <tt>packaging</tt> element is JAR so you do not have to
specify this for most projects.</li>
<li><b>version</b> This element indicates the version of the artifact
generated by the project. Maven goes a long way to help you with version
management and you will often see the <tt>SNAPSHOT</tt> designator in a
version, which indicates that a project is in a state of development. We will
discuss the use of <a
href="./index.html#What_is_a_SNAPSHOT_version">snapshots</a> and how they work
further on in this guide.</li>
@@ -712,7 +712,7 @@ Results :
<li><tt>**/Abstract*Test.java</tt></li>
<li><tt>**/Abstract*TestCase.java</tt></li></ul>
<p>You have walked through the process for setting up, building, testing,
packaging, and installing a typical Maven project. This is likely the vast
majority of what projects will be doing with Maven and if you've noticed,
everything you've been able to do up to this point has been driven by an
18-line file, namely the project's model or POM. If you look at a typical Ant
<a href="../../ant/build-a1.xml">build file</a> that provides the same
functionality that we've achieved thus far you'll notice it's already twice the
size of the POM and we're just getting started! There is far more functionality
available to you from Maven without requiring any additions to our POM as it
currently stands. To get any more functionality out of our example Ant build
file you must keep making error-prone additions.</p>
-<p>So what else can you get for free? There are a great number of Maven
plug-ins that work out of the box with even a simple POM like we have above.
We'll mention one here specifically as it is one of the highly prized features
of Maven: without any work on your part this POM has enough information to
generate a web site for your project! You will most likely want to customize
your Maven site but if you're pressed for time all you need to do to provide
basic information about your project is execute the following command:</p>
+<p>So what else can you get for free? There are a great number of Maven
plugins that work out of the box with even a simple POM like we have above.
We'll mention one here specifically as it is one of the highly prized features
of Maven: without any work on your part this POM has enough information to
generate a web site for your project! You will most likely want to customize
your Maven site but if you're pressed for time all you need to do to provide
basic information about your project is execute the following command:</p>
<div class="source"><pre class="prettyprint linenums">mvn site</pre></div>
<p>There are plenty of other standalone goals that can be executed as well,
for example:</p>
<div class="source"><pre class="prettyprint linenums">mvn clean</pre></div>
@@ -759,7 +759,7 @@ Results :
...</pre></div>
<p>You'll notice that all plugins in Maven 2.0 look much like a dependency -
and in some ways they are. This plugin will be automatically downloaded and
used - including a specific version if you request it (the default is to use
the latest available).</p>
<p>The <tt>configuration</tt> element applies the given parameters to every
goal from the compiler plugin. In the above case, the compiler plugin is
already used as part of the build process and this just changes the
configuration. It is also possible to add new goals to the process, and
configure specific goals. For information on this, see the <a
href="../introduction/introduction-to-the-lifecycle.html"> Introduction to the
Build Lifecycle</a>.</p>
-<p>To find out what configuration is available for a plugin, you can see the
<a href="../../plugins/"> Plugins List</a> and navigate to the plugin and goal
you are using. For general information about how to configure the available
parameters of a plugin, have a look at the <a
href="../mini/guide-configuring-plugins.html">Guide to Configuring
Plug-ins</a>.</p></div>
+<p>To find out what configuration is available for a plugin, you can see the
<a href="../../plugins/"> Plugins List</a> and navigate to the plugin and goal
you are using. For general information about how to configure the available
parameters of a plugin, have a look at the <a
href="../mini/guide-configuring-plugins.html">Guide to Configuring
Plugins</a>.</p></div>
<div class="section">
<h3><a name="How_do_I_add_resources_to_my_JAR">How do I add resources to my
JAR?</a></h3>
<p>Another common use case that can be satisfied which requires no changes to
the POM that we have above is packaging resources in the JAR file. For this
common task, Maven again relies on the <a
href="../introduction/introduction-to-the-standard-directory-layout.html">Standard
Directory Layout</a>, which means by using standard Maven conventions you can
package resources within JARs simply by placing those resources in a standard
directory structure.</p>
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
