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

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-775:
-----------------------------

    Fix Version/s:     (was: 2.1)
                   Shared Components

> Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
> ----------------------------------------------------------------------------------------------
>
>                 Key: MNG-775
>                 URL: http://jira.codehaus.org/browse/MNG-775
>             Project: Maven 2
>          Issue Type: New Feature
>          Components: maven-archiver
>    Affects Versions: 2.0-alpha-3
>            Reporter: John Casey
>            Priority: Minor
>             Fix For: Shared Components
>
>   Original Estimate: 6 hours
>          Time Spent: 6 hours
>  Remaining Estimate: 0 minutes
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira