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

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

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

Michael Osipov closed MECLIPSE-456.
-----------------------------------
    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.

> Allow for manifest customization
> --------------------------------
>
>                 Key: MECLIPSE-456
>                 URL: https://issues.apache.org/jira/browse/MECLIPSE-456
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)