From ec56fbd2bdf93d4870333f52e70acfd62d2d008c Mon Sep 17 00:00:00 2001 From: Brett Porter Date: Mon, 21 Jan 2008 11:34:26 +0000 Subject: [PATCH] doc clarification git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@613848 13f79535-47bb-0310-9956-ffa450edef68 --- .../src/site/apt/adminguide/legacy.apt | 52 ++++++++++++------- 1 file changed, 32 insertions(+), 20 deletions(-) diff --git a/archiva-docs/src/site/apt/adminguide/legacy.apt b/archiva-docs/src/site/apt/adminguide/legacy.apt index 79fd5bac2..238429d38 100644 --- a/archiva-docs/src/site/apt/adminguide/legacy.apt +++ b/archiva-docs/src/site/apt/adminguide/legacy.apt @@ -1,32 +1,44 @@ ------ - Apache Archiva legacy support configuration + Apache Archiva legacy repository support configuration ------ -Apache Archiva legacy support configuration +Apache Archiva legacy repository 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 + Archiva supports both Maven 1 and Maven 2 clients transparently when used as a proxy. The + underlying managed repository can use either the default or legacy layout, and Archiva will + convert the requested path to the expected internal format. + + However, 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 - and this is not always deterministic. + The strategy used by Archiva has been tested on many existing artifacts in the public central + repository, but users may require support for private artifacts or for artifacts with classifiers. - Since version 1.1, archiva provides a legacy support configuration to the administrator. It + Since version 1.0.1, 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 : + reference. Archiva will check that the entered artifact reference matches + the legacy path, to avoid corrupted data in repository. + + For example: + + * Path: <<>> + + * Group ID: <<>> - path -> custom artifact reference -> path MUST equals + * Artifact ID: <<>> + + * Version: <<<1.0-FCS>>> + + * Classifier: <<>> + + * Type: <<>> + + This prevents the artifact incorrectly getting translated to a version of <<<1.0>>> and a classifier of <<>>. 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. + By default, <<>> is registered, as it is used by some core + Maven 1 plugins (however this is not the case if you upgraded from a previous + version and retained your configuration file). -- 2.39.5