svn commit: r379658 - in /maven/site/trunk/src/site/apt/guides: index.apt mini/guide-deploying-3rd-party-jars.apt

[ar...@apache.org]

Author: aramirez
Date: Tue Feb 21 18:46:59 2006
New Revision: 379658

URL: http://svn.apache.org/viewcvs?rev=379658&view=rev
Log:
PR: MDEPLOY-25

-added documentation on how to deploy 3rd party jars, also mentioned that it would be installed both on local and remote repository

Added:
    maven/site/trunk/src/site/apt/guides/mini/guide-deploying-3rd-party-jars.apt
Modified:
    maven/site/trunk/src/site/apt/guides/index.apt

Modified: maven/site/trunk/src/site/apt/guides/index.apt
URL: http://svn.apache.org/viewcvs/maven/site/trunk/src/site/apt/guides/index.apt?rev=379658&r1=379657&r2=379658&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/index.apt (original)
+++ maven/site/trunk/src/site/apt/guides/index.apt Tue Feb 21 18:46:59 2006
@@ -50,6 +50,8 @@
 
  * {{{mini/guide-installing-3rd-party-jars.html}Guide to installing 3rd party JARs}}
 
+ * {{{mini/guide-deploying-3rd-party-jars.html}Guide to deploying 3rd party JARs to remote repository}}
+
  * {{{mini/guide-m1-m2.html}Guide to Moving From Maven 1.x to Maven 2.x}}
 
  * {{{mini/guide-manifest.html}Guide to Working with Manifests}}

Added: maven/site/trunk/src/site/apt/guides/mini/guide-deploying-3rd-party-jars.apt
URL: http://svn.apache.org/viewcvs/maven/site/trunk/src/site/apt/guides/mini/guide-deploying-3rd-party-jars.apt?rev=379658&view=auto
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-deploying-3rd-party-jars.apt (added)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-deploying-3rd-party-jars.apt Tue Feb 21 18:46:59 2006
@@ -0,0 +1,59 @@
+ ------
+ Guide to deploying 3rd party JARs to remote repository
+ ------
+ Allan Ramirez
+ ------
+ 22 February 2006
+ ------
+
+Guide to deploying 3rd party JARs to remote repository
+
+ Same concept of the {{{guide-installing-3rd-party-jars.html}install:install-file}}
+ goal of the maven-install-plugin where the 3rd party JAR is installed 
+ in the local repository. But this time instead to local repository the 
+ JAR will be install both in the local and remote repository. 
+
+ To deploy a 3rd party JAR use the deploy:deploy-file goal under 
+ maven-deploy-plugin.
+
+ First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to 
+ your %M2_HOME%/lib.
+
+ Then execute the command:
+
++----+
+mvn deploy:deploy-file -DgroupId=<group-id> \
+	-DartifactId=<artifact-id> \
+	-Dversion=<version> \
+	-Dpackaging=<type-of-packaging> \
+	-Dfile=<path-to-file> \
+	-DrepositoryId=<id-to-map-on-server-section-of-settings.xml> \
+	-Durl=<url-of-the-repositor-to-deploy>
++----+
+
+* Deploying a 3rd party JAR with a generic POM
+
+  By default, deploy:deploy-file generates a generic POM(.pom) to be deploy 
+  together with the 3rd party JAR. To disable this feature we should set the 
+  <<<generatePOM>>> argument to false.
+
++----+
+-DgeneratePom=false
++----+
+
+* Deploying a 3rd party JAR with a customed POM
+
+  If a POM is already existing for the 3rd Party JAR and you want to deploy 
+  it together with the JAR we should use the <<<pomFile>>> argument of the 
+  deploy-file goal. See sample below.
+
++----+
+mvn deploy:deploy-file -DpomFile=<path-to-pom> \
+	-Dfile=<path-to-file> \
+	-DrepositoryId=<id-to-map-on-server-section-of-settings.xml> \
+	-Durl=<url-of-the-repositor-to-deploy>  
++----+
+
+  Note that <<<groupId>>>, <<<artifactId>>>, <<<version>>> and <<<packaging>>> 
+  arguments are not included here because deploy-file goal will get these 
+  information from the given POM. 
\ No newline at end of file