You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Martin Stockhammer (JIRA)" <ji...@apache.org> on 2018/04/17 20:04:00 UTC
[jira] [Commented] (MRM-1964) Refactor repository api
[ https://issues.apache.org/jira/browse/MRM-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441418#comment-16441418 ]
Martin Stockhammer commented on MRM-1964:
-----------------------------------------
Still work in progress. RepositoryRegistry is mostly used in modules instead of RepositoryAdmin.
I'm separating the maven specific parts into their own modules
> 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
> Fix For: 3.0.0
>
>
> 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
(v7.6.3#76005)