From 5c54962dfe747a67901fceb36eac82300df8dcce Mon Sep 17 00:00:00 2001 From: Henri Yandell Date: Fri, 24 Nov 2006 21:47:09 +0000 Subject: [PATCH] Applying Daniel Mohni's excellent documentation on using Archiva from Maven. git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@479011 13f79535-47bb-0310-9956-ffa450edef68 --- .../getting-started/maven-configuration.apt | 171 ++++++++++++++++++ src/site/site.xml | 1 + 2 files changed, 172 insertions(+) create mode 100644 src/site/apt/guides/getting-started/maven-configuration.apt diff --git a/src/site/apt/guides/getting-started/maven-configuration.apt b/src/site/apt/guides/getting-started/maven-configuration.apt new file mode 100644 index 000000000..7d498c0c9 --- /dev/null +++ b/src/site/apt/guides/getting-started/maven-configuration.apt @@ -0,0 +1,171 @@ + ----- + Client Configuration + ----- + ----- + 17 November 2006 + ----- + +~~ Copyright 2006 The Apache Software Foundation. +~~ +~~ Licensed under the Apache License, Version 2.0 (the "License"); +~~ you may not use this file except in compliance with the License. +~~ You may obtain a copy of the License at +~~ +~~ http://www.apache.org/licenses/LICENSE-2.0 +~~ +~~ Unless required by applicable law or agreed to in writing, software +~~ distributed under the License is distributed on an "AS IS" BASIS, +~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +~~ See the License for the specific language governing permissions and +~~ limitations under the License. + +~~ NOTE: For help with the syntax of this file, see: +~~ http://maven.apache.org/guides/mini/guide-apt-format.html + +Configuring Maven-2 to use an Archiva repository + + To get your local Maven 2 installation to use an Archiva proxy you need to add the repositories you require to your 'settings.xml'. This file is usually found in ${user.dir}/.m2/settings.xml (see the {{{http://maven.apache.org/settings.html}Settings Reference}}). + + You will need to add one entry for each repository that is setup in Archiva. If your repository contains plugins; remember to also include a setting. + + => where to find Archiva eg. http://localhost:8080/archiva + + => Identifer for the proxied repository inside Archiva + + => Another identifier, this time for normal repositories [one of the these will go away] + + +* Configuring a Repository + + [[1]] create a new profile to setup your repositories + ++-------------------------------------------------------------------------+ + + ... + + + Repository Proxy + + true + + + + + + + ... + + ... + + + + + + + ... + + ... + + + ... + + ... + ++-------------------------------------------------------------------------+ + + [[2]] add your repository configuration to the profile... + + You can copy the repository configuration from the POM Snippet on the Archiva Administration Page for a normal repository. It should look much like: + ++-------------------------------------------------------------------------+ + + repository-1 + URL-TO-ARCHIVA/repository/URL-NAME + + true + + + false + + ++-------------------------------------------------------------------------+ + + You can also copy this for a proxied repository, but make sure to change /repository/ to /proxy/ and to change from the "URL Name" to the "Repository Identifier". This should look much like this: + ++-------------------------------------------------------------------------+ + + maven-release + URL-TO-ARCHIVA/proxy/REPOSITORY-ID + + true + + + false + + ++-------------------------------------------------------------------------+ + + +* 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} + + ... + + ... + ++-------------------------------------------------------------------------+ + + [[4]] 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/ + + + ... + ++-------------------------------------------------------------------------+ + + [[5]] Add a build extension to your pom.xml to use webdav + ++-------------------------------------------------------------------------+ + + ... + + + + org.apache.maven.wagon + wagon-webdav + 1.0-beta-1 + + + + ... + ++-------------------------------------------------------------------------+ + + [[6]] Finally the user that is running archiva (tomcat-user, plexus-user,..) must have write access to the deployment repository. diff --git a/src/site/site.xml b/src/site/site.xml index 9ac73bd7b..547c61c58 100644 --- a/src/site/site.xml +++ b/src/site/site.xml @@ -26,6 +26,7 @@ + -- 2.39.5