blob: 79fd5bac2c7f91a64d3cf603910eb0908116d468 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
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.
Since version 1.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 :
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.
|
