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

JFrog Artifactory Documentation

Products: JFrog Artifactory
Content Type: User Guide

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

MavenMaven Repositories
GradleWorking with Gradle
IvyWorking with Ivy
SBT

Field	Description
Checksum Policy	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: Verify against client checksums (default) - If a client has not sent a valid checksum for a deployed artifact then Artifactory will return a 404 (not found) error to a client trying to access that checksum. If the client has sent a checksum, but it conflicts with the one calculated on the server then Artifactory will return a 409 (conflict) error until a valid checksum is deployed. Trust server generated checksums - Artifactory will not verify checksums sent by clients and will trust the server's locally calculated checksums. An uploaded artifact is immediately available for use, but integrity might be compromised.
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: Unique: Uses a unique, time-based version number. Nonunique: Uses the default self-overriding naming pattern: `artifactID-version-SNAPSHOT.type` Deployer: Uses the format sent by the deployer as is. Deployer parameter option Metadata will not be generated when selecting the Deployer option. This option should not be used when setting up replication, since each Artifactory instance will need to generate its metadata locally. 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. Blank (default) indicates that there is no limit on the number of unique snapshots.
Handle Releases	When set, enables you to deploy release artifacts into this repository.
Handle Snapshots	When set, enables 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 `groupId:artifactId:version` in the POM is consistent with the deployed path. If there is a conflict between these then Artifactory will reject the deployment. You can disable this behavior by setting this checkbox.