Author: wsmoak
Date: Sun Mar 11 17:47:38 2007
New Revision: 517058
URL: http://svn.apache.org/viewvc?view=rev&rev=517058
Log:
Add a section on deploying third-party artifacts to Archiva using webdav.
Modified:
maven/archiva/trunk/archiva-site/src/site/apt/guides/getting-started/maven-configuration.apt
Modified:
maven/archiva/trunk/archiva-site/src/site/apt/guides/getting-started/maven-configuration.apt
URL:
http://svn.apache.org/viewvc/maven/archiva/trunk/archiva-site/src/site/apt/guides/getting-started/maven-configuration.apt?view=diff&rev=517058&r1=517057&r2=517058
==============================================================================
---
maven/archiva/trunk/archiva-site/src/site/apt/guides/getting-started/maven-configuration.apt
(original)
+++
maven/archiva/trunk/archiva-site/src/site/apt/guides/getting-started/maven-configuration.apt
Sun Mar 11 17:47:38 2007
@@ -132,7 +132,9 @@
</settings>
+-------------------------------------------------------------------------+
- [[4]] Configure the distributionManagement part of your pom.xml
+* Deploying to Archiva
+
+ [[1]] Configure the distributionManagement part of your pom.xml
+-------------------------------------------------------------------------+
<project>
@@ -153,7 +155,7 @@
</project>
+-------------------------------------------------------------------------+
- [[5]] Add a build extension to your pom.xml to use webdav
+ [[2]] Add a build extension to your pom.xml to use webdav
+-------------------------------------------------------------------------+
<project>
@@ -171,4 +173,45 @@
</project>
+-------------------------------------------------------------------------+
- [[6]] Finally the user that is running archiva (tomcat-user, plexus-user,..)
must have write access to the deployment repository.
+ [[3]] Finally the user that is running archiva (tomcat-user, plexus-user,..)
must have write access to the deployment repository.
+
+* Deploying Third-Party Artifacts to Archiva
+
+ [[1]] In the directory from which you intend to execute "<<<mvn
+ deploy:deploy-file>>>", save the following content as <<<pom.xml>>>.
+
++-------+
+<project>
+ <modelVersion>4.0.0</modelVersion>
+ <groupId>com.example</groupId>
+ <artifactId>webdav-deploy</artifactId>
+ <packaging>pom</packaging>
+ <version>1</version>
+ <name>Webdav Deployment POM</name>
+
+ <build>
+ <extensions>
+ <extension>
+ <groupId>org.apache.maven.wagon</groupId>
+ <artifactId>wagon-webdav</artifactId>
+ <version>1.0-beta-2</version>
+ </extension>
+ </extensions>
+ </build>
+
+</project>
++-------+
+
+ This pom will not be deployed with the artifact, it simply serves to make the
+ wagon-webdav jar available to the build process.
+
+ Alternately, save this file somewhere else, and use "<<<mvn ... -f
+ /path/to/filename>>>" to force the use of an alternate POM file.
+
+ [[2]] Deploy the artifact:
+
++------+
+mvn deploy:deploy-file -Dfile=filename.jar -DpomFile=filename.pom
+ -DrepositoryId=deployment.webdav
+ -Durl=dav:URL-TO-ARCHIVA/repository/REPOSITORY-ID
++------+
