Maven Shared Components
  1. Maven Shared Components
  2. MSHARED-26

Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number

    Details

    • Type: New Feature New Feature
    • Status: Reopened Reopened
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: maven-archiver
    • Labels:
      None
    • Number of attachments :
      0

      Description

      From MNG-251:

      bit of a chicken and egg problem under the current arch. I want to include:

      • the build number as a separate manifest entry
      • the correct version in the manifest and META-INF/maven/pom.xml

      However, the snapshot is only determined when the artifact is transformed for install - which comes after package.

      I think this may need to be a phase before package, or part of an existing phase, or that packaging actually does the version assignment, and install/deploy just utilises it.

      More thinking required.

        Issue Links

          Activity

          Hide
          John Casey added a comment -

          I'm recreating this issue, to properly account for time.

          Show
          John Casey added a comment - I'm recreating this issue, to properly account for time.
          Hide
          John Casey added a comment -

          If we're to have a single snapshot build-id for artifacts and attachments, then it will have to be generated ahead of the install/deploy process, which means it's a no-brainer to also include in the artifacts themselves, somewhere under META-INF possibly.

          Show
          John Casey added a comment - If we're to have a single snapshot build-id for artifacts and attachments, then it will have to be generated ahead of the install/deploy process, which means it's a no-brainer to also include in the artifacts themselves, somewhere under META-INF possibly.
          Hide
          John Casey added a comment -

          single build number is used per artifact-set (artifact plus attachments, defined by g:a), but NOT per reactor, since individual builds of sub-projects could lead to build numbers falling out of sync.

          Show
          John Casey added a comment - single build number is used per artifact-set (artifact plus attachments, defined by g:a), but NOT per reactor, since individual builds of sub-projects could lead to build numbers falling out of sync.
          Hide
          Brett Porter added a comment -

          rolled back. wasn't working.

          due to low priority, we'll leave this for later.

          Show
          Brett Porter added a comment - rolled back. wasn't working. due to low priority, we'll leave this for later.

            People

            • Assignee:
              Unassigned
              Reporter:
              John Casey
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - 6 hours
                6h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 6 hours
                6h