---- Repository APIs ---- ~~ Licensed to the Apache Software Foundation (ASF) under one ~~ or more contributor license agreements. See the NOTICE file ~~ distributed with this work for additional information ~~ regarding copyright ownership. The ASF licenses this file ~~ to you under the Apache License, Version 2.0 (the ~~ "License"); you may not use this file except in compliance ~~ with the License. You may obtain a copy of the License at ~~ ~~ http://www.apache.org/licenses/LICENSE-2.0 ~~ ~~ Unless required by applicable law or agreed to in writing, ~~ software distributed under the License is distributed on an ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~~ KIND, either express or implied. See the License for the ~~ specific language governing permissions and limitations ~~ under the License. Repository APIs The repository APIs are the means for accessing metadata from any type of repository. currently, only metadata retrieval is available. As more of the application moves to this base, artifact content may be read using a stream, for example. * Metadata Resolver A repository request works in the following sequence: [[1]] the user requests a project's metadata using a {{{./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 [[3]] the metadata is retrieved, and if not up to date in the metadata repository it is stored there [[4]] the metadata is returned to the requester * Storage Resolver Currently storage only supports obtaining information as well. In the future, the ability to modify the storage will be made available for plugins such as purging, etc. More information can be found in the {{{./apidocs/reference/org/apache/archiva/metadata/repository/storage/StorageMetadataResolver.html} storage metadata resolver}} class.