You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/05/04 08:19:12 UTC
[jira] Issue Comment Edited: (MRM-1360) Separate Maven 2.x
functionality into a separate plugin
[ http://jira.codehaus.org/browse/MRM-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219802#action_219802 ]
Brett Porter edited comment on MRM-1360 at 5/4/10 1:17 AM:
-----------------------------------------------------------
we should move the metadata update consumer into this plugin as well and remove its dependency on archiva-repository-layer and archiva-model
It has the following uses in MUC:
- ProjectReference, VersionedReference and ArtifactReference
- MetadataTools and related APIs
- ManagedRepositoryContent / RepositoryContentFactory
was (Author: brettporter):
we should move the metadata update consumer into this plugin as well and remove its dependency on archiva-repository-layer and archiva-model
> Separate Maven 2.x functionality into a separate plugin
> -------------------------------------------------------
>
> Key: MRM-1360
> URL: http://jira.codehaus.org/browse/MRM-1360
> Project: Archiva
> Issue Type: Improvement
> Components: Maven 2 Support
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.4
>
>
> Similarly to MRM-1359, the Maven 2 repository functionality should be self contained in a plugin
--
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