archiva-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nico...@apache.org
Subject svn commit: r603897 - in /maven/archiva/trunk/archiva-docs/src/site/apt/adminguide: configuration.apt legacy.apt
Date Thu, 13 Dec 2007 11:55:48 GMT
Author: nicolas
Date: Thu Dec 13 03:55:43 2007
New Revision: 603897

URL: http://svn.apache.org/viewvc?rev=603897&view=rev
Log:
MRM-594 doc

Added:
    maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/legacy.apt
Modified:
    maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/configuration.apt

Modified: maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/configuration.apt
URL: http://svn.apache.org/viewvc/maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/configuration.apt?rev=603897&r1=603896&r2=603897&view=diff
==============================================================================
--- maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/configuration.apt (original)
+++ maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/configuration.apt Thu Dec 13
03:55:43 2007
@@ -14,6 +14,8 @@
 
     * {{{network-proxies.html} Configuring network proxies}}
 
+    * {{{legacy.html} Configuring legacy (maven 1) support}}
+
     * {{{consumers.html} Configuring repository scanning and consumers}}
 
     []

Added: maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/legacy.apt
URL: http://svn.apache.org/viewvc/maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/legacy.apt?rev=603897&view=auto
==============================================================================
--- maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/legacy.apt (added)
+++ maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/legacy.apt Thu Dec 13 03:55:43
2007
@@ -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.
+  
+



Mime
View raw message