[
http://jira.codehaus.org/browse/MRM-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225926#action_225926
]
Maria Odea Ching commented on MRM-980:
--------------------------------------
I've broken down the rest of the items that needs to be done and set some
target dates (relative to the proposed timeline for GSoC):
* repository merge API (June 30)
- repo merger
- unit tests
* UI for repository merge (July 11)
- button to merge repo
- page showing conflicting artifacts
- confirmation page
- integration with repo merge API
* webapp tests (July 19)
* security (July 23)
* audit logging (July 31)
Eshan, are you ok with the target dates?
> 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: SourceAritfacts.java, stage-repository-merge.patch,
> stage-repository-merge.patch, stage-repository-merge.patch,
> stage-repository-merge.patch, stage-repository-merge.zip
>
>
> 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
