[
http://jira.codehaus.org/browse/MRM-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patti Arachchige Eshan Sudharaka updated MRM-980:
-------------------------------------------------
Attachment: ArtifactsMerger.java
here i have fixed issue regarding copying the POM files and the coding
convention problem. And also updating project maven metadata is done using
repository api. but i am still confusing why we cannot just copy version
metadata xml (if it exists in the source artifact in the source repository ).
since project meta data xml is depends on available versions i used API to
update it.
> 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: ArtifactsMerger.java, ArtifactsMerger.java,
> ArtifactsMerger.java, 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.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
