[jira] [Closed] (MSHARED-26) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MSHARED-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MSHARED-26.
---------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
> ----------------------------------------------------------------------------------------------
>
>                 Key: MSHARED-26
>                 URL: https://issues.apache.org/jira/browse/MSHARED-26
>             Project: Maven Shared Components
>          Issue Type: New Feature
>          Components: maven-archiver
>            Reporter: John Casey
>            Priority: Minor
>   Original Estimate: 6h
>          Time Spent: 6h
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)