[
http://jira.codehaus.org/browse/MRM-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229074#action_229074
]
Maria Odea Ching commented on MRM-980:
--------------------------------------
Applied latest patch to MRM-980 branch in
[-r965157|http://svn.apache.org/viewvc?revision=965157&view=revision].
I noted a few things that need to be fixed:
# The repositories page is broken. See attached screenshot
MRM-980-broken-repos-page.png
# Display/show the url of the attached staging repository in the repositories
page so it would be easier to know when deploying from command line
# Maybe we can only have "Merge" in the Merge Actions in repositories page,
then have the "Merge All" and "Merge with Skip" in the following page where the
list of artifacts that are conflicting are listed.
# What about in the artifact web browse? After the merge is done, should the
repository ID of the artifact be changed to the managed repo instead of the
staging one?
# The merging doesn't seem to be working. I uploaded an artifact (from Upload
Artifact in webapp) to the staging repo then clicked "Merge All". When I
checked the managed repo, the artifact I uploaded in the staging repo wasn't
merged.
Thanks!
> 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,
> archiva-modules.patch, archiva-modules.patch, archiva-modules.patch,
> archiva-modules.patch, archiva-modules.patch, archiva-modules.patch,
> archiva-modules.patch, archiva-webapp.patch, ArtifactsMerger.java,
> ArtifactsMerger.java, ArtifactsMerger.java, ArtifactsMerger.java,
> MRM-980-broken-repos-page.png, 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.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-with-conflict-artifacts.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
