From 7b407f8e1de11591eab40c185e1d00bcb533abf5 Mon Sep 17 00:00:00 2001 From: Nicolas De Loof Date: Thu, 13 Dec 2007 11:55:43 +0000 Subject: [PATCH] MRM-594 doc git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@603897 13f79535-47bb-0310-9956-ffa450edef68 --- .../src/site/apt/adminguide/configuration.apt | 2 ++ .../src/site/apt/adminguide/legacy.apt | 32 +++++++++++++++++++ 2 files changed, 34 insertions(+) create mode 100644 archiva-docs/src/site/apt/adminguide/legacy.apt diff --git a/archiva-docs/src/site/apt/adminguide/configuration.apt b/archiva-docs/src/site/apt/adminguide/configuration.apt index ee0e6c769..346f7f206 100644 --- 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 index 000000000..4982109b5 --- /dev/null +++ b/archiva-docs/src/site/apt/adminguide/legacy.apt @@ -0,0 +1,32 @@ + ------ + Apache Archiva legacy support configuration + ------ + +Apache Archiva legacy support configuration + + Archiva supports both maven 1 and maven 2 clients when used as a proxy. The + underlying managed repository can use default or legacy layout, archiva will + convert the request path to the expected internal format. + +* path to artifact conversion + + Due to the lack of structure in maven 1 "legacy" artifact request format, + archiva must split the request path to discover artifactId, version and + classifier. There is no fully deterministis way to extract the artifactId + and version, and classifiers are simply unsupported. The strategy used + by archiva has been tested on many existing artifacts in the public central + repository, but users may require support for private artifact or for + artifacts with classifiers. + + Archiva provides a legacy support configuration to the administrator. It + is possible to register some custom legacy path and the expected artifact + reference. Archiva will check that the entered artifact reference match + the legacy path, to avoid corrupted datas in repository : + + path -> custom artifact reference -> path MUST equals + + Those custom legacy path are stored in the archiva.xml configuration file. + By default, jaxen-1.0-FCS-full is registered, as it is used by some core + maven 1 plugins. + + -- 2.39.5