You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2005/01/28 07:33:27 UTC

[jira] Updated: (MPWAR-40) include build.number in Implementation-Version in manifest

The following issue has been updated:

    Updater: Jonathan W. Cranford (mailto:jcranford4@cox.net)
       Date: Fri, 28 Jan 2005 1:32 AM
    Comment:
patch mentioned in Issue Description above
    Changes:
             Attachment changed to maven-war-plugin-build.number.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MPWAR-40?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPWAR-40

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPWAR-40
    Summary: include build.number in Implementation-Version in manifest
       Type: New Feature

     Status: Unassigned
   Priority: Minor

 Original Estimate: 1 hour
 Time Spent: Unknown
  Remaining: 1 hour

    Project: maven-war-plugin
   Versions:
             1.6

   Assignee: 
   Reporter: Jonathan W. Cranford

    Created: Fri, 28 Jan 2005 1:31 AM
    Updated: Fri, 28 Jan 2005 1:32 AM
Environment: maven-1.0.2
maven-war-plugin-1.6.1
plugin.jelly, v1.46

Description:
As of the version stated in the Environment field, ${pom.currentVersion} is used for the both the Specification-Version and the Implementation-Version when creating the manifest for the war.

It'd be nice if the Implementation-Version could include a build number as well, like the one maintained by the Ant buildnumber task.

I have a patch I'll upload that sets the Implementation-Version to "${pom.currentVersion}, build ${build.number}", if build.number is already set.

To use the enhancement, just call ant:buildnumber in a preGoal of war:war.

I can't think of another way to provide this functionality, so I decided to go ahead and patch plugin.jelly.  When I started this endeavor, I thought I absolutely had to have this feature, but now that it's done, I could probably live without it.  Oh well, that's the way it goes. :)  Hence the minor priority.

Let me know what you think.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org