From: Olivier Lamy Date: Sat, 27 Oct 2012 21:01:36 +0000 (+0000) Subject: fix links X-Git-Tag: archiva-1.4-M4~697 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=d8e7bd8193e725a8dd539ecf922ce3493d231024;p=archiva.git fix links git-svn-id: https://svn.apache.org/repos/asf/archiva/trunk@1402869 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/archiva-modules/src/site/apt/metadata-api.apt b/archiva-modules/src/site/apt/metadata-api.apt index 01bd63f76..fc7ab9b59 100644 --- a/archiva-modules/src/site/apt/metadata-api.apt +++ b/archiva-modules/src/site/apt/metadata-api.apt @@ -33,22 +33,22 @@ Metadata API and Persistence The Java model is a very simply representation of the metadata. Presently the following are represented: - * {{{./apidocs/org/apache/archiva/metadata/model/MetadataFacet.html} repository metadata facets}} + * {{{./apidocs/reference/org/apache/archiva/metadata/model/MetadataFacet.html} repository metadata facets}} - * {{{./apidocs/org/apache/archiva/metadata/model/ProjectMetadata.html} project metadata}} + * {{{./apidocs/reference/org/apache/archiva/metadata/model/ProjectMetadata.html} project metadata}} - * {{{./apidocs/org/apache/archiva/metadata/model/ProjectVersionMetadata.html} project version metadata}} + * {{{./apidocs/reference/org/apache/archiva/metadata/model/ProjectVersionMetadata.html} project version metadata}} * various subtypes More information can be found in the - {{{./apidocs/org/apache/archiva/metadata/model/package-summary.html} org.apache.archiva.metadata.model}} package, + {{{./apidocs/reference/org/apache/archiva/metadata/model/package-summary.html} org.apache.archiva.metadata.model}} package, or the {{{./metadata/metadata-model/index.html} metadata-model}} module. * Metadata Repository API The metadata repository API is responsible for accessing the metadata repository and persisting changes. This is - handled by the {{{./apidocs/org/apache/archiva/metadata/repository/MetadataRepository.html} MetadataRepository}} + handled by the {{{./apidocs/reference/org/apache/archiva/metadata/repository/MetadataRepository.html} MetadataRepository}} class. More information can be found in the {{{./metadata/metadata-repository-api/index.html} metadata-repository-api}} @@ -58,6 +58,6 @@ Metadata API and Persistence Currently, the only implementation of persistence for the metadata content is a flat-file option using Java properties. The code is note yet production quality. You can find out more in the: - {{{./apidocs/org/apache/archiva/metadata/repository/file/FileMetadataRepository.html} FileMetadataRepository}} + {{{./apidocs/reference/org/apache/archiva/metadata/repository/file/FileMetadataRepository.html} FileMetadataRepository}} class. diff --git a/archiva-modules/src/site/apt/repository-api.apt b/archiva-modules/src/site/apt/repository-api.apt index a4c00dad0..590c993b3 100644 --- a/archiva-modules/src/site/apt/repository-api.apt +++ b/archiva-modules/src/site/apt/repository-api.apt @@ -31,7 +31,7 @@ Repository APIs A repository request works in the following sequence: [[1]] the user requests a project's metadata using a - {{{./apidocs/org/apache/archiva/metadata/repository/MetadataResolver.html} MetadataResolver}} + {{{./apidocs/reference/org/apache/archiva/metadata/repository/MetadataResolver.html} MetadataResolver}} [[2]] the resolvers are chained together to locate the source of the metadata, and to determine where the most up to date copy is. Included by default are the metadata repository and repository storage @@ -46,5 +46,5 @@ Repository APIs will be made available for plugins such as purging, etc. More information can be found in the - {{{./apidocs/org/apache/archiva/metadata/repository/storage/StorageMetadataResolver.html} storage metadata resolver}} + {{{./apidocs/reference/org/apache/archiva/metadata/repository/storage/StorageMetadataResolver.html} storage metadata resolver}} class.