Repository Management with Nexus
A.7. Configuring Artifactory Repository Imports

A.7. Configuring Artifactory Repository Imports

The second table in Step 2 of the Artifactory Import panel is the Repositories panel. In this panel you can select repositories to import and also configure how Artifactory proxy repositories would be mapped to Nexus proxy repository with matching canonical URLs. Each row in the Repositories table contains the following columns:

Import
This column contains a simple checkbox. If the checkbox is checked, the repository will be imported into Nexus. If the checkbox is not check, the Nexus Migration plugin will omit the repository from the import process.
Repository ID
This is the repository identifier from Artifactory. This column cannot be edited.
Type
This is the type of the repository being imported. Hosted repositories in Artifactory will be imported as hosted repositories in Nexus. Proxy repositories in Artifactory will be imported as proxy repositories in Nexus unless they are merged with an existing proxy repository.
Map URLs
Since Nexus is a drop-in replacement for Artifactory, the Nexus Migration Plugin gives you the option to Map the legacy Artifactory URLs to the newer Nexus URLs. Checking this box will tell the Nexus Migration plugin to create the appropriate URL mappings to allow clients to interact with the newly created Nexus repositories via the legacy Artifactory URLs.
Copy Cached Artifacts
Checking this box will tell the Nexus Migration plugin to copy the cache contents of a proxy repository to the newly created Nexus repository. Leaving this box unchecked will tell the Nexus Migration plugin to only copy the configuration for a proxy repository.
Releases/Snapshots
This allows you to customize the Repository Policy in a newly created Nexus repository. If you want a hosted or proxy repository to serve only release or snapshot versions, select the corresponding value in the drop-down. If you want a host or proxy repository to serve both release and snapshot versions, select both in this drop-down list. If you want Nexus to use the type implied by the Artifactory repository, don’t select a value in this drop-down.
Merge With
If an Artifactory proxy repository has a canonical URL which matches the canonical URL of an existing Nexus repository, you can merge this proxy repository into the existing Nexus proxy repository. Most people running the Artifactory Import process will likely have a repo1 proxy repository in Artifactory for the Maven Central repository and a central proxy repository in Nexus for the Maven Central repository. As both of these repositories have the same URL, the Nexus Migration plugin will show a checkbox in the Merge With column as shown in Figure A.6, “Merging a Proxy Repository During Artifactory Import”. Checking this box will instruct the Nexus Migration plugin to merge the contents and configuration of the repo1 repository with the existing central repository. In other words, if this box is checked, the Nexus Migration plugin will not create a new proxy repository for repo1, and if the box isn’t checked, the Nexus Migration plugin will create new proxy repository for repo1
figs/web/artifactory_merging-proxy-repos.png

Figure A.6. Merging a Proxy Repository During Artifactory Import


Sonatype Promotion Subscribe via RSS