Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: 
 <13138529.1213314013646.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Thu, 12 Jun 2008 18:40:13 -0500 (CDT)
From: "Brett Porter (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Subject: [jira] Moved: (MSHARED-26) Reissue of MNG-251: maven-archiver
 should be able to include the snapshot version/build number
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Brett Porter moved MNG-775 to MSHARED-26:
-----------------------------------------

    Affects Version/s:     (was: 2.0-alpha-3)
        Fix Version/s:     (was: Shared Components)
          Component/s:     (was: maven-archiver)
                       maven-archiver
                  Key: MSHARED-26  (was: MNG-775)
              Project: Maven Shared Components  (was: Maven 2)

> Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
> ----------------------------------------------------------------------------------------------
>
>                 Key: MSHARED-26
>                 URL: http://jira.codehaus.org/browse/MSHARED-26
>             Project: Maven Shared Components
>          Issue Type: New Feature
>          Components: maven-archiver
>            Reporter: John Casey
>            Priority: Minor
>   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