[
https://issues.apache.org/jira/browse/MRM-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234176#comment-16234176
]
Martin Stockhammer commented on MRM-1964:
-----------------------------------------
Added repository registry and moved the repository admin implementation to the
new API.
Changed the repository interfaces where applicable.
Next tasks:
* move the indexing part to the provider/registry.
* clarify the repositoryContent bean usages - it seems there are singleton
beans used, but stored per repository id with direct references.
* move usage of repositoryContentFactory to repository registry
> Refactor repository api
> -----------------------
>
> Key: MRM-1964
> URL: https://issues.apache.org/jira/browse/MRM-1964
> Project: Archiva
> Issue Type: Improvement
> Reporter: Martin Stockhammer
> Assignee: Martin Stockhammer
> Priority: Major
>
> Currently, the repository access managed via the repository admin api and has
> several specifics in it that are highly dependent on the repository
> implementation.
> At the time there is no way to provide another repository type without
> changing/duplicating code on a lot of different places.
> Another issue, is that many modules are dependent on maven libraries.
> Goal is to provide a central repository registry, that keeps track of
> repositories and delegates provider specific tasks to special repository
> providers.
> Maven libraries should only be used in the repository provider
> implementations. All other modules should use the central repository api.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
