MRM-594 doc

git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@603897 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/archiva-docs/src/site/apt/adminguide/configuration.apt b/archiva-docs/src/site/apt/adminguide/configuration.apt
index ee0e6c769d5ec7354b53221b0a00a0871358816b..346f7f2061e59427d1df5dbc337cbc75c47b43dd 100644 (file)
--- a/archiva-docs/src/site/apt/adminguide/configuration.apt
+++ b/archiva-docs/src/site/apt/adminguide/configuration.apt
@@ -14,6 +14,8 @@ Runtime Configuration of Apache Archiva
 
     * {{{network-proxies.html} Configuring network proxies}}
 
+    * {{{legacy.html} Configuring legacy (maven 1) support}}
+
     * {{{consumers.html} Configuring repository scanning and consumers}}
 
     []

diff --git a/archiva-docs/src/site/apt/adminguide/legacy.apt b/archiva-docs/src/site/apt/adminguide/legacy.apt
new file mode 100644 (file)
index 0000000..4982109
--- /dev/null
+++ b/archiva-docs/src/site/apt/adminguide/legacy.apt
@@ -0,0 +1,32 @@
+ ------\r
+ Apache Archiva legacy support configuration\r
+ ------\r
+\r
+Apache Archiva legacy support configuration\r
+\r
+  Archiva supports both maven 1 and maven 2 clients when used as a proxy. The\r
+  underlying managed repository can use default or legacy layout, archiva will\r
+  convert the request path to the expected internal format.\r
+  \r
+* path to artifact conversion\r
+  \r
+  Due to the lack of structure in maven 1 "legacy" artifact request format, \r
+  archiva must split the request path to discover artifactId, version and \r
+  classifier. There is no fully deterministis way to extract the artifactId\r
+  and version, and classifiers are simply unsupported. The strategy used\r
+  by archiva has been tested on many existing artifacts in the public central\r
+  repository, but users may require support for private artifact or for \r
+  artifacts with classifiers.\r
+  \r
+  Archiva provides a legacy support configuration to the administrator. It\r
+  is possible to register some custom legacy path and the expected artifact \r
+  reference. Archiva will check that the entered artifact reference match\r
+  the legacy path, to avoid corrupted datas in repository :\r
+  \r
+  path -> custom artifact reference -> path MUST equals\r
+  \r
+  Those custom legacy path are stored in the archiva.xml configuration file.\r
+  By default, jaxen-1.0-FCS-full is registered, as it is used by some core\r
+  maven 1 plugins.\r
+  \r
+\r