maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vsive...@apache.org
Subject svn commit: r611174 - /maven/site/trunk/src/site/apt/guides/mini/guide-3rd-party-jars-remote.apt
Date Fri, 11 Jan 2008 13:40:45 GMT
Author: vsiveton
Date: Fri Jan 11 05:40:44 2008
New Revision: 611174

URL: http://svn.apache.org/viewvc?rev=611174&view=rev
Log:
MNG-2947: Deploy 3rd party source jar
Submitted by: Daniel Siegmann

o applied

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

Modified: maven/site/trunk/src/site/apt/guides/mini/guide-3rd-party-jars-remote.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-3rd-party-jars-remote.apt?rev=611174&r1=611173&r2=611174&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-3rd-party-jars-remote.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-3rd-party-jars-remote.apt Fri Jan 11 05:40:44
2008
@@ -9,32 +9,32 @@
 Guide to deploying 3rd party JARs to remote repository
 
  Same concept of the {{{./guide-3rd-party-jars-local.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. 
+ 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 
+ 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 
+ 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>
+  -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 
+  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.
 
 +----+
@@ -43,17 +43,22 @@
 
 * 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 
+  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>  
+  -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
+  Note that <<<groupId>>>, <<<artifactId>>>, <<<version>>>
and <<<packaging>>>
+  arguments are not included here because deploy-file goal will get these
+  information from the given POM.
+
+* Deploying Source Jars
+
+ To deploy a 3rd party source jar, packaging should be set to <<<java-source>>>,
and
+ generatePom should be set to <<<false>>>.



Mime
View raw message