Modules and Path Patterns used by Repository Layouts

JFrog Artifactory Documentation

ft:sourceType
Paligo

To support smart module management, Artifactory must construct module information for stored files. Artifactory constructs this information based on path pattern information defined as part of the Repository Layout configuration (detailed below).

A module is comprised of various sub-elements or fields, which are typically expressed in the path of a stored artifact.

The module-sub elements recognized by Artifactory are listed below. At a minimum, there are three mandatory fields required for module identification:

  • Organization

  • Module

  • Base Revision

Field

Description

Example

Mandatory

Organization

A sequence of literals that identifies the artifact's organization

"org.slf4j"

Module

A sequence of literals that identifies the artifact's module

"slf4j-api"

Base Revision

A sequence of literals that identifies the base revision part of the artifact version, excluding any integration information

"1.5.10", or in case of an integration revision "1.2-SNAPSHOT" the base revision is "1.2"

Folder Integration Revision

A sequence of literals that identifies the integration revision part used in folder names in the artifact's path, excluding the base revision

in case of an integration revision "1.2-SNAPSHOT" the folder integration revision is "SNAPSHOT"

File Integration Revision

A sequence of literals that identifies the integration revision part in the artifact's file name, excluding the base revision

in case of an integration revision "1.2-20110202.144533-3" the file integration revision is "20110202.144533-3"

Classifier

A sequence of literals that identifies the artifact's classifier

"sources"

Extension

A sequence of literals that identifies the artifact's extension

"zip"

Type

A sequence of literals that identifies the artifact's type.

Typically used when the artifact's extension cannot be reused as the artifact's type

"java-source"