To configure a local repository, hover over it with your mouse and select "Edit" to display the Edit Local Repository dialog.
Common Basic Settings
The following are fully described in the Common Settings page.
Additional Basic Settings
Sets the layout that the repository should use for storing and identifying modules.
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:
- 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:
- Deployer: Uses the format sent by the deployer as is.
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 youchange 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.
Suppress POM Consistency Checks
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 Artifcatory will reject the deployment. You can disable this behavior by setting this checkbox.
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)
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)