From: Brett Porter Date: Fri, 23 Nov 2007 04:15:01 +0000 (+0000) Subject: add deployment docs X-Git-Tag: archiva-1.0~16 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=4082f028be06922c94c3a53929e8019d0a06c435;p=archiva.git add deployment docs git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@597541 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/archiva-docs/src/site/apt/guides/maven-configuration.apt b/archiva-docs/src/site/apt/guides/maven-configuration.apt index 26fb1447a..b107239a1 100644 --- a/archiva-docs/src/site/apt/guides/maven-configuration.apt +++ b/archiva-docs/src/site/apt/guides/maven-configuration.apt @@ -92,113 +92,6 @@ Configuring Maven-2 to use an Archiva repository +-------------------------------------------------------------------------+ -* Configuring Maven-2 to deploy to an Archiva repository - - [[1]] Create a user in Archiva to use for deployment - - [[2]] The deployment user needs the Role 'Repository Manager' for each repository that you want to deploy to - - [[3]] Define the server for deployment inside your 'settings.xml', use the newly created user for authentication - -+-------------------------------------------------------------------------+ - - ... - - - deployment.webdav - {archiva-deployment-user} - {archiva-deployment-pwd} - - ... - - ... - -+-------------------------------------------------------------------------+ - -* Deploying to Archiva - - [[1]] Configure the distributionManagement part of your pom.xml - -+-------------------------------------------------------------------------+ - - ... - - - deployment.webdav - Internal Release Repository - dav:URL-TO-ARCHIVA/repository/REPOSITORY-ID/ - - - deployment.webdav - Internal Snapshot Repository - dav:URL-TO-ARCHIVA/repository/REPOSITORY-ID/ - - - ... - -+-------------------------------------------------------------------------+ - - [[2]] Add a build extension to your pom.xml to use webdav - -+-------------------------------------------------------------------------+ - - ... - - - - org.apache.maven.wagon - wagon-webdav - 1.0-beta-2 - - - - ... - -+-------------------------------------------------------------------------+ - - [[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 "<<>>", save the following content as <<>>. - -+-------+ - - 4.0.0 - com.example - webdav-deploy - pom - 1 - Webdav Deployment POM - - - - - org.apache.maven.wagon - wagon-webdav - 1.0-beta-2 - - - - - -+-------+ - - 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 "<<>>" 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 -+------+ - Archiva as a Proxy * Creating a New Proxy Repository @@ -264,4 +157,4 @@ Archiva as a Proxy Execute a Maven 2 build. Artifacts should be downloaded from the proxy repository/repositories you've set in your settings.xml - \ No newline at end of file + diff --git a/archiva-docs/src/site/apt/userguide/deploy.apt b/archiva-docs/src/site/apt/userguide/deploy.apt index 30fbbdb48..342121479 100644 --- a/archiva-docs/src/site/apt/userguide/deploy.apt +++ b/archiva-docs/src/site/apt/userguide/deploy.apt @@ -4,5 +4,119 @@ Deploying to Repository - :STUB: This is a documentation stub. +* Configuring Maven to deploy to an Archiva repository + + [[1]] Create a user in Archiva to use for deployment + [[2]] The deployment user needs the Role 'Repository Manager' for each repository that you want to deploy to + + [[3]] Define the server for deployment inside your 'settings.xml', use the newly created user for authentication + ++-------------------------------------------------------------------------+ + + ... + + + deployment.webdav + {archiva-deployment-user} + {archiva-deployment-pwd} + + ... + + ... + ++-------------------------------------------------------------------------+ + +* Deploying to Archiva using WebDAV + + [[1]] Configure the <<>> part of your <<>> (customising the URLs as needed) + ++-------------------------------------------------------------------------+ + + ... + + + archiva.internal + Internal Release Repository + dav:http://reposerver.mycompany.com:8080/archiva/repository/internal/ + + + archiva.snapshots + Internal Snapshot Repository + dav:http://reposerver.mycompany.com:8080/archiva/repository/snapshots/ + + + ... + ++-------------------------------------------------------------------------+ + + [[2]] Add a build extension to your <<>> + ++-------------------------------------------------------------------------+ + + ... + + + + org.apache.maven.wagon + wagon-webdav + 1.0-beta-2 + + + + ... + ++-------------------------------------------------------------------------+ + + [[3]] Finally the user that is running archiva (tomcat-user, plexus-user,..) must have write access to the deployment repository. + +* Deploying using other protocols + + You can also deploy to the Archiva server using traditional means such as SCP, FTP, etc. For more information on these deployment + techniques, refer to the Maven documentation. + + Note that once the files are deployed into the location of the Archiva managed repository, they will not be detected by Archiva until the + next scan takes place, so the interval should be configured to a reasonably frequent setting. + +* Deploying Third-Party Artifacts to Archiva + + [[1]] In the directory from which you intend to execute "<<>>", save the following content as <<>>. + ++-------+ + + 4.0.0 + com.example + webdav-deploy + pom + 1 + Webdav Deployment POM + + + + + org.apache.maven.wagon + wagon-webdav + 1.0-beta-2 + + + + + ++-------+ + + 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 "<<>>" 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:http://repo.mycompany.com:8080/repository/internal/ ++------+ + +~~TODO: information for Maven 1, ant tasks, ivy, etc.