[
http://jira.codehaus.org/browse/MRM-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patti Arachchige Eshan Sudharaka updated MRM-980:
-------------------------------------------------
Attachment: archiva-modules.patch
meta data updating and getArtifact() method is moved from merge module.
> Ability to merge repositories
> -----------------------------
>
> Key: MRM-980
> URL: http://jira.codehaus.org/browse/MRM-980
> Project: Archiva
> Issue Type: New Feature
> Reporter: Wendy Smoak
> Fix For: Backlog
>
> Attachments: archiva-modules.patch, archiva-modules.patch,
> ArtifactsMerger.java, ArtifactsMerger.java, ArtifactsMerger.java,
> ArtifactsMerger.java, resources.zip, SourceAritfacts.java,
> stage-repository-merge.patch, stage-repository-merge.patch,
> stage-repository-merge.patch, stage-repository-merge.patch,
> stage-repository-merge.patch, stage-repository-merge.patch,
> stage-repository-merge.patch, stage-repository-merge.patch,
> stage-repository-merge.zip, test-repository.patch
>
>
> Need to be able to merge one repository into another, updating metadata and
> not overwriting existing artifacts.
> The source repository should remain unchanged.
> It should produce output listing what was merged and what wasn't.
> Additions to the target repo should show in the audit log.
> Related thread: http://www.nabble.com/Merging-repositories-ts19850359.html
--
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
