nexus2artifactory | tool designed to ease migration | Data Migration library
kandi X-RAY | nexus2artifactory Summary
kandi X-RAY | nexus2artifactory Summary
This tool is designed to ease the transition from Sonatype Nexus to JFrog Artifactory. It provides a simple wizard-like interface that allows you to easily configure and run a migration of repositories, artifacts, users, and settings from a Nexus instance to an Artifactory instance. Currently, the following data can be migrated: - local (hosted), remote (proxy), and virtual (group) repositories - note that Bower repositories are not yet supported - artifacts stored in local (hosted) repositories - artifacts stored in remote caches are NOT currently migrated - users, groups (roles), and permissions (privileges) - LDAP configurations. Note that due to limitations in the REST API in Artifactory OSS, this tool can only migrate to licensed Artifactory distributions (Pro, Enterprise, etc). It does not work with free distributions (OSS, CE, etc).
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of nexus2artifactory
nexus2artifactory Key Features
nexus2artifactory Examples and Code Snippets
Community Discussions
Trending Discussions on nexus2artifactory
QUESTION
I'm using nexus2artifactory tool to migrate form nexus to artifactory (as tool's name obviously says) and am facing a strange behavior and was wondering if I'm doing something wrong.
I'm trying to migrate some maven repositories created on nexus which handle snapshots and which should be set with UNIQUE as "Maven Snapshot Version Behavior" (default when creating a maven repo in Artifactory) but after the migration all my snapshots repos are set with NON-UNIQUE which is quite annoying especially when using maven3 where the support for uniqueVersion tag was dropped.
Am I alone with this problem ? What can I do to migrate these repos differently ?
Thank you in advance for your kind explanation
...ANSWER
Answered 2017-Jun-21 at 11:00The reason for this behaviour is that the nexus2artifactory tool is using the Artifactory REST API for creating the repositories.
The default value for snapshotVersionBehavior when working with the REST API is non-unique (for legacy reasons).
This should be fixed in the nexus2artifactory tool (and possibly also change the REST API defaults). In the meantime, if you need a quick fix, the following could be added to Artifactory.py:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install nexus2artifactory
This tool’s interface uses the ncurses library, which is standard in Linux and MacOS, but not readily available in Windows. Instead, the tool can use the PDCurses library as an alternative. This means that Windows users must also have the latest version of [PDCurses][] to run the tool. Alternatively, Windows users may avoid installing any dependencies by downloading the self-contained [exe file][]. [PDCurses]: http://pdcurses.sourceforge.net/ [exe file]: https://github.com/JFrogDev/nexus2artifactory/raw/master/NexusToArtifactory.exe.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page