Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.2
-
Component/s: None
-
Labels:None
Description
There are two main use cases that we need to support for users migrating from another repo manager or from a badly designed CI based sharing system.
First, a repo must be separated into two repos, snapshots and releases. Don't bother cleaning the metadata because Nexus itself will do this. Next, there should be a mode to convert a local repository into a remote repository format.
The tool for migrating the data should be a separate command line tool that we will bundle into Nexus. It should ask for the location of the source data and a destination for the migrated data. The user should be asked to copy or move the files. (copy is safer but may not be possible if the repo is huge)
The rules for converting the local repo format will be documented in its subtask.
Attachments
1.
|
Repo Conversion: Separate a mixed snap/release repo into two repos |
|
Closed | Unassigned | ||||||||
2.
|
Repo Conversion: Convert local repo format into remote repo format |
|
Closed | Unassigned | ||||||||
3.
|
Make changes to text when conversion is successful |
|
Closed | Unassigned | ||||||||
4.
|
Version option gives 'Unable determine version from JAR file.' error |
|
Closed | Unassigned | ||||||||
5.
|
Help option produces 'Unable to parse command line options: -r-o' message and does not display help options |
|
Closed | Unassigned | ||||||||
6.
|
Move option produces 'Unable to parse command line options: Unrecognized option: -m' error |
|
Closed | Unassigned | ||||||||
7.
|
Change the spelling of conversion for the jar (and project name) and success message |
|
Closed | Unassigned |
|
