You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@archiva.apache.org by sk...@apache.org on 2012/08/29 20:47:38 UTC
svn commit: r1378678 -
/archiva/trunk/archiva-modules/src/site/apt/index.apt.vm
Author: skygo
Date: Wed Aug 29 18:47:38 2012
New Revision: 1378678
URL: http://svn.apache.org/viewvc?rev=1378678&view=rev
Log:
fix badlink
Modified:
archiva/trunk/archiva-modules/src/site/apt/index.apt.vm
Modified: archiva/trunk/archiva-modules/src/site/apt/index.apt.vm
URL: http://svn.apache.org/viewvc/archiva/trunk/archiva-modules/src/site/apt/index.apt.vm?rev=1378678&r1=1378677&r2=1378678&view=diff
==============================================================================
--- archiva/trunk/archiva-modules/src/site/apt/index.apt.vm (original)
+++ archiva/trunk/archiva-modules/src/site/apt/index.apt.vm Wed Aug 29 18:47:38 2012
@@ -49,7 +49,7 @@ Archiva Developer's Documentation
Similarly, the resolution strategy for resources in the repository is abstracted from the storage and metadata to
allow multiple strategies. This facilitates features such as repository proxying, repository grouping, and on the
- fly format conversion. These are described in the {{{./repositories.html} Repository API}} documents.
+ fly format conversion. These are described in the {{{./repository-api.html} Repository API}} documents.
On top of the metadata repository, components can be built to provide the services available in the application.
These are described as plugins, though at this time there is no formal plugin registration mechanism or interface -