We are very new in using Artifactory services, we would like to store all our artifacts in JFrog Artifactory server for dependency as well as for release management. I have currently created one Local Repository in the name 'myartifactory' and I am planning to use the following code in my projects pom.xml file for distribution management.
<distributionManagement> <repository> <id>central</id> <name>jd-releases</name> <url>http://jd-msg.staging.com/artifactory/myartifactory</url> </repository> <snapshotRepository> <id>snapshots</id> <name>jd-snapshots</name> <url>http://jd-msg.staging.com/artifactory/myartifactory</url> </snapshotRepository> </distributionManagement>
Does the above method looks like a recommended way? How about having "Remote Repositories" and "Virtual Repositories"? Is it mandatory to have? What is the real life example for those?
In addition artifactory by default recommends some best practices for Local Repositories like the following,
Pre-defined Local Repositories: - Artifactory comes with a set of pre-defined local repositories, which reflect best practices in binary repository management as follows:
libs-release-local - Your code releases libs-snapshot-local - Your code snapshots ext-release-local - Manually deployed 3rd party libs (releases) ext-snapshot-local - Manually deployed 3rd party libs (shapshots) plugins-release-local - Your and 3rd party plugins (releases) plugins-snapshot-local - Your and 3rd party plugins (snapshots)
So I am bit confused about the right approach. Suggestions are welcome.