svn commit: r293442 - /maven/components/trunk/maven-site/src/site/apt/guides/getting-started/index.apt

[jv...@apache.org]

Author: jvanzyl
Date: Mon Oct  3 12:46:30 2005
New Revision: 293442

URL: http://svn.apache.org/viewcvs?rev=293442&view=rev
Log: (empty)

Modified:
    maven/components/trunk/maven-site/src/site/apt/guides/getting-started/index.apt

Modified: maven/components/trunk/maven-site/src/site/apt/guides/getting-started/index.apt
URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/apt/guides/getting-started/index.apt?rev=293442&r1=293441&r2=293442&view=diff
==============================================================================
--- maven/components/trunk/maven-site/src/site/apt/guides/getting-started/index.apt (original)
+++ maven/components/trunk/maven-site/src/site/apt/guides/getting-started/index.apt Mon Oct  3 12:46:30 2005
@@ -129,7 +129,8 @@
   * <<packaging>> This element indicates the packing to be used by this artifact. 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. This
     is a topic we will deal with further on in the guide, just keep in mind the indicated packaging of a project
-    can play a part in customizing the build lifecycle.
+    can play a part in customizing the build lifecycle. The default value for the <<<packaging>>> element is JAR
+    so you do not have to specify this for most projects.
 
   * <<version>> 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 <<<SNAPSHOT>>> designator in a version which
@@ -285,7 +286,25 @@
 
 * How do I create a JAR and install it in my local repository?
 
+ Making a JAR file is straight forward enough and can be accomplished by executing the following command:
+
++----+
+
+m2 package
+
++----+
+
+ If you again take a look at the POM for this project you will notice the <<<packaging>>> element is set to <<<jar>>>.
+ This is how Maven knows to produce a JAR file from the above command. You can now take a look in the the
+ <<<${basedir}/target>>> directory and you will see the generated JAR file.
+
++----+
+
+m2 install
+
 +----+
+
+
 +----+
 
 ~~* How do I package resources inside my JAR?
@@ -295,8 +314,6 @@
 
 ~~* How do I filter resources against my POM?
 
-+-----+
-
 FYI - In beta-2, while the other technique is still supported, the
 recommended way is finally settled:
 
@@ -307,8 +324,6 @@
     <filtersFile>...</filtersFile>
   </filters>
 </build>
-
-+-----+
 
 ~~* How do use resources with my tests?
 ~~  o EIDSL



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org