Reposilite works slightly different than Artifactory or Nexus, so make sure you've properly configured your instance and environment.
Guides you may find especially useful during migration:
Be sure to check the .m2 compatible export box to get an export that Reposilite can use. Also, we recommend excluding artifactory build metadata if your version of Artifactory has this feature.
Move the resulting export files to your new Reposilite server and extract them to the repository folder you would like them in.
Depending on the organization of your new repositories, you may need to move your artifacts out of parent folders to get them in the location you want them in your new repository.
Configure the new repository in Reposilite, if you haven't already, making sure it is loading files from the correct directory.
You should be able to browse the artifacts once configuration reloads.
In some cases, you may want to merge separated release and snapshot repositories into one Reposilite repository. Rsync offers a useful way to do this and is installed by default on many unix systems. The following command safely merges releases in a releases folder into a snapshots folder containing snapshots. You can then move / rename the snapshots folder accordingly.
# Merge all files in releases into the snapshots folder
$ rsync -avhu --progress ./releases/ ./snapshots/
# Remove the releases folder
$ rm -rf ./releases
# Move the contents of the snapshots folder to your final target repository
$ mv ./snapshots/* /data/reposilite/repositories/my-migrated-repository/
If your Artifactory exports contain build metadata folders that you would prefer to remove, you can use the following command to help remove them. This command performs a find for all directories, in the current directory, ending in .artifactory-metadata, and removes them from the system.
$ rm -rf `find. -type d -name *.artifactory-metadata`
Did you find misleading or deprecated content? Maybe you just feel this section misses important elements?