Uploaded image for project: 'Jenkins Artifactory Plug-in'
  1. Jenkins Artifactory Plug-in
  2. HAP-263

Staging: Support more complex artifact version schemes


    • Type: Improvement
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Common, Release Management
    • Labels:


      Currently, only versions of the following formats are correctly parsed: a.b.c.d...[-e] (examples: 1.2.3, 1.2.3-4,,, etc.)
      It is desired that a more complex version format is correctly interpreted so that the numbers are incremented accordingly when there is a version upgrade due to the release process.

      The suggested format is:
      <primary_components>[ -][<annotation><[ -]annotation_revision>][<[ -_]snapshot_specifier>]

      • <primary_components>: <major[>.<minor[>.<incremental1[>.<incremental2...]]]>
        Positive integers separated by '.'. Example: The first three components are named: major, minor, and incremental, respectively. The rest of the primary components can be classified as "subincrementals" (currently, Maven doesn't support these).
      • <annotation>: Sequence of letters that usually describe the release type. Examples: alpha, beta, RC, etc.
      • <annotation_revision>: A positive integer associated to the annotation.
      • <snapshot_specifier>: SNAPSHOT

      Examples: 1, 1.2, 1.2.3,, 1.2-SNAPSHOT, 1.2-alpha-3, 1.2.3-beta-4, 1.2.3rc4

      You should take into account that versions may need to be compared and the comparison should be case insensitive and compare digits appropriately.

      The following are some references that show how Maven is tending to support more complex version schemes:




            • Assignee:
              yossis Yossi Shaul
              ngrobisa Nicolas Grobisa
            • Votes:
              1 Vote for this issue
              1 Start watching this issue


              • Created: