[
http://jira.codehaus.org/browse/MRM-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219808#action_219808
]
Brett Porter commented on MRM-1347:
-----------------------------------
BTW, here are the references I found to the model and repository layer that
we'd be aiming to remove. It's probably not a one-for-one substitution in this
case due to the redesign.
Keys (for debug logging) and RepositoryURL in DRPC; ArtifactReference in DRPC,
RPC; RepositoryConnectors from repo-layer could be folded into this module in
some way; MetadataTools (and others in that package) used for merging in DRPC
can be pushed back into the maven2 repository implementation,
ManagedRepositoryContent and RepositoryContentFactory are used quite a bit for
path calculation in DRPC which would move to the storage (means rethinking the
tmpdir calculation and how to get the connectors), RemoteRepositoryContent is
something that needs to be rethought and perhaps added to the metadata
repository API.
> Migrate repository proxy to the new repository API
> --------------------------------------------------
>
> Key: MRM-1347
> URL: http://jira.codehaus.org/browse/MRM-1347
> Project: Archiva
> Issue Type: Task
> Components: remote proxy
> Reporter: Maria Odea Ching
> Fix For: 1.4
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
