minor fix for link in apt file

git-svn-id: https://svn.apache.org/repos/asf/archiva/trunk@1391263 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
skygo 2012-09-27 23:45:28 +00:00
parent 72112d7be4
commit a3059b8939
2 changed files with 3 additions and 3 deletions

View File

@ -28,9 +28,9 @@ Deploying to Repository
There are different ways on how you can deploy artifacts in an Archiva repository.
* {{Maven}} Configuring Maven to deploy to an Archiva repository}}
* {{Maven}} Configuring Maven to deploy to an Archiva repository
* {{Web UI}} Deploying via the Web UI Form}}
* {{Web UI}} Deploying via the Web UI Form
Starting with Archiva 1.2.3, it is possible to block re-deployment of released artifacts to a specific repository. This can be configured through the
repository configuration page by ticking the <<<Block Re-deployment of Released Artifacts>>> checkbox.

View File

@ -21,7 +21,7 @@
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}}).
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}}).
How you configure the settings depends on how you would like to utilise the repository. You can add the Archiva repository as an additional repository to others already declared by the project, or lock down the
environment to only use the Archiva repositories (possibly proxying content from a remote repository).