Additional Settings for Maven/Gradle/Ivy/SBT Remote Repositories

JFrog Artifactory Documentation

Products: JFrog Artifactory
Content Type: User Guide
ft:sourceType: Paligo

In addition to the basic settings that are common for all remote repositories, there are specific settings for the following package types:

Maven
GradleWorking with Gradle
IvyWorking with Ivy
SBT

Field	Description
Checksum Policy	Checking the Checksum effectively verifies the integrity of a deployed resource. The Checksum Policy determines how the system behaves when a client checksum for a remote resource is missing or conflicts with the locally calculated checksum. There are four options: Generate if absent (default): The system attempts to retrieve the remote checksum, If it is not found, the system will automatically generate one and fetch the artifact. If the remote checksum does not match the locally calculated checksum, the artifact will not be cached and the download will fail. Fail: If the remote checksum does not match the locally calculated checksum, or is not found, the artifact will not be cached and the download will fail. Ignore and generate: The system ignores the remote checksum and only uses the locally generated one. As a result, remote artifact retrieval never fails, however integrity of the retrieved artifact may be compromised. Ignore and pass-through: The system stores and passes through all remote checksums (even if they do not match the locally generated one). If a remote checksum is not found, Artifactory generates one locally. As a result, remote resource retrieval never fails, however integrity of the retrieved artifact may be compromised, and client side checksum validation (as performed by Maven, for example) will fail.
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.
Eagerly Fetch Jars	When set, if a POM is requested, Artifactory attempts to fetch the corresponding jar in the background. This will accelerate first access time to the jar when it is subsequently requested.
Suppress POM Consistency Checks	By default, the system keeps your repositories healthy by refusing POMs with incorrect coordinates (path). If the `groupId:artifactId:version` information inside the POM does not match the deployed path, Artifactory rejects the deployment with a "409 Conflict" error. You can disable this behavior by setting the Suppress POM Consistency checkbox.
Eagerly Fetch Sources	When set, if a binaries jar is requested, Artifactory attempts to fetch the corresponding source jar in the background. This will accelerate the initial access time to the source jar when it is subsequently requested.
Handle Releases	If set, Artifactory enables you to deploy or cache release artifacts into this repository.
Handle Snapshots	If set, Artifactory enables you to deploy or cache snapshot artifacts into this repository.