jvanzyl 2003/02/12 17:12:20
Modified: xdocs/reference user-guide.xml
Log:
o Maven JAR override doco.
Revision Changes Path
1.32 +60 -3 jakarta-turbine-maven/xdocs/reference/user-guide.xml
Index: user-guide.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/reference/user-guide.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- user-guide.xml 11 Feb 2003 16:45:08 -0000 1.31
+++ user-guide.xml 13 Feb 2003 01:12:20 -0000 1.32
@@ -300,11 +300,12 @@
Here's the sample maven.xml
</p>
<source><![CDATA[
-<project default="nightly-build"
- xmlns:j="jelly:core"
+<project
+ default="nightly-build"
xmlns:m="maven"
+ xmlns:j="jelly:core"
xmlns:u="jelly:util">
-
+
<goal name="nightly-build">
<!-- Any ant task, or jelly tags can go here thanks to jeez -->
<j:set var="goals" value="compile,test" />
@@ -681,6 +682,62 @@
</subsection>
<subsection name="Overriding Stated Dependencies">
+ <p>
+ You may find it convenient, or necessary, at times to override the
+ dependencies stated in a given POM. You may wish to use JAR artifacts
+ somewhere in the filesystem or you may wish simply to override the stated
+ version of a given JAR artifact. For this Maven provides the a
+ an easy way for you to select which artifacts you want to use for
+ building. It is highly recommended that you set up your own local
+ repository: but in cases where expediency is a concern, or you are
+ migrating from an Ant build the JAR override feature may come
+ in handy.
+ </p>
+
+ <p>
+ In order to use the JAR override feature, you must set the
+ <code>maven.jar.override</code> property on. Once this property is
+ set you can specify JAR override directives in any of the properties
+ files that maven processes.
+ </p>
+
+ <p>
+ There are two type of JAR override directives. The first form allows
+ you to specify a specific JAR artifact path for a given artifactId; the
+ second allows you to specify a specific version of a JAR artfact that
+ exists in your local repository. The two forms are as follows:
+ </p>
+
+<source><[CDATA[
+
+maven.jar.artifactId = [path]
+
+maven.jar.artifactId = [version]
+
+]]/></source>
+
+ <p>
+ Below is an example of what a properties file might look like that
+ contains JAR override directives:
+ </p>
+
+<source><[CDATA[
+# ------------------------------------------------------------------------
+# M A V E N J A R O V E R R I D E
+# ------------------------------------------------------------------------
+maven.jar.override = on
+
+# ------------------------------------------------------------------------
+# Jars set explicity by path.
+# ------------------------------------------------------------------------
+maven.jar.a = ${basedir}/lib/a.jar
+maven.jar.b = ${basedir}/lib/b.jar
+
+# ------------------------------------------------------------------------
+# Jars set explicity by version.
+# ------------------------------------------------------------------------
+maven.jar.classworlds = 1.0-beta-1
+]]/></source>
</subsection>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
