[jira] Updated: (MECLIPSE-456) Allow for manifest customization

["Arnaud Heritier (JIRA)" <ji...@codehaus.org>]

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

Arnaud Heritier updated MECLIPSE-456:
-------------------------------------

    Component/s: Core : Dependencies resolution and build path (.classpath)

> Allow for manifest customization
> --------------------------------
>
>                 Key: MECLIPSE-456
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-456
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.5.1
>            Reporter: Michael Johns
>            Priority: Minor
>
> It would be nice to have the ability to customize the manifest, much the same way the maven-jar-plugin and maven-war-plugin allow.  They use the maven-archiver.  See http://maven.apache.org/shared/maven-archiver/examples/manifest.html for some ideas of what can be accomplished.
> Our application reads some information from the manifest dynamically to let us know what version of the code we've deployed, and while it works great when built and deployed on the server, we can't make it work in our dev environments due to how the plugin limits what we can put in the manifest.

-- 
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