Need help with other JFrog products?
Using the latest JFrog Artifactory version? See the documentation here.
Additional Basic Settings
Repositories may have additional Basic settings depending on the Package Type.
Maven, Gradle, Ivy and SBT Repositories
Maven, Gradle, Ivy and SBT repositories share the same additional Basic settings.
Checking the Checksum effectively verifies the integrity of a deployed resource. The Checksum Policy determines how Artifactory behaves when a client checksum for a deployed resource is missing or conflicts with the locally calculated checksum.
There are two options:
Maven Snapshot Version Behavior
Artifactory supports centralized control of how snapshots are deployed into a repository, regardless of end user-specific settings. This can be used to guarantee a standardized format for deployed snapshots within your organization. There are three options:
Maven 3 Only Supports Unique Snapshots
Maven 3 has dropped support for resolving and deploying non-unique snapshots. Therefore, if you have a snapshot repository using non-unique snapshots, we recommend that you change your Maven snapshot policy to 'Unique' and remove any previously deployed snapshots from this repository.
The unique snapshot name generated by the Maven client on deployment cannot help in identifying the source control changes from which the snapshot was built and has no relation to the time sources were checked out. Therefore,we recommend that the artifact itself should embed the revision/tag (as part of its name or internally) for clear and visible revision tracking. Artifactory allows you to tag artifacts with the revision number as part of its Build Integration support.
Max Unique Snapshots
|Specifies the maximum number of unique snapshots of the same artifact that should be stored. Once this number is reached and a new snapshot is uploaded, the oldest stored snapshot is removed automatically.|
A value of 0 (default) indicates that there is no limit on the number of unique snapshots.
If set, Artifactory allows you to deploy release artifacts into this repository.
|If set, Artifactory allows you to deploy snapshot artifacts into this repository.|
Suppress POM Consistency
|When deploying an artifact to a repository, Artifactory verifies that the value set for |
If there is a conflict between these then Artifcatory will reject the deployment. You can disable this behavior by setting this checkbox.
Other Repository Types
For other type-specific repository configuration, please refer to the corresponding repository page under Artifactory Pro.
Select Property Sets
|Defines the property sets that will be available for artifacts stored in this repository.|
|If set, Artifactory ignores this repository when trying to resolve artifacts. The repository is also not available for download or deployment of artifacts.|
Allow Content Browsing
If set, allows you to view file contents (e.g., Javadoc browsing, HTML files) directly from Artifactory.
When content browsing is allowed we recommend strict content moderation to ensure that any uploaded content does not compromise security (for example, cross-site scripting attacks)
The Replications tab lets you define and edit replication settings for the repository. For details, please refer to Repository Replication.
Pre-defined Local Repositories
Artifactory comes with a set of pre-defined local repositories, which reflect best practices in binary repository management as follows:
Your code releases
Your code snapshots
Manually deployed 3rd party libs (releases)
Manually deployed 3rd party libs (shapshots)
Your and 3rd party plugins (releases)
Your and 3rd party plugins (snapshots)