Apache/archiva
1
0
Fork 0
mirror of https://github.com/apache/archiva.git synced 2025-02-22 10:17:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

MRM-594 doc

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@603897 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Nicolas De Loof 2007-12-13 11:55:43 +00:00
parent 44d4643ddb
commit 7b407f8e1d
2 changed files with 34 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
archiva-docs/src/site/apt/adminguide/configuration.apt
View File

@ -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}}
[]

32
archiva-docs/src/site/apt/adminguide/legacy.apt Normal file
View File

@ -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.