manifest.mf is overwritten by eclipse during jar export

Question

I would like make an executable jar archive with eclipse. So into my project I created file src/META-INF/MANIFEST.MF :

Manifest-Version: 1.0
Main-Class: MainClass
Class-Path: .

But when I export my java eclipse project eclipse warn me with following message:

"JAR export finished with warnings. See details for additional information. myproject/src/META-INF/MANIFEST.MF was replaced by the generated MANIFEST.MF and is no longer in the JAR."

Anyone know how I can avoid this when I export my project in eclipse?

Digressive

Answer 1

While exporting the jar, select the option to use existing manifest and browse to the manifest file of your project. The generated jar will have that manifest file now.

Using existing manifest http://img46.imageshack.us/img46/6752/export.png

Quattlebaum

This no longer works in current Eclipse, as of 2015-09-17. – Indusium

@sventechie: The Eclipse Wizard can do a few simple things. If you need something more complex, use the command line and Ant or Maven. – Kammerer

@AaronDigulla This is a very common, simple need for Java developers and Eclipse can no longer do it. Not only will it not generate it for you but it won't allow you to make a custom manifest either -- it will always be overwritten. Being dismissive is not helpful. – Indusium

@Indusium Since IBM left, development speed of core Eclipse has slowed to glacial speeds. You can try to open a bug but my gut feeling is that it will have 3+ years before anyone can look at it. Sorry. – Kammerer

Answer 2

Using Oxygen (Release 4.7.0), I was able to do this successfully. The confusing part is that on the JAR File Specification page of the JAR Export wizard, both the Next and Finish buttons are active. So if you don't notice that and just click Finish, you'll end up with a warning (and the generated manifest). To use your own, click Next instead (once for JAR Packaging Options, and again for JAR Manifest Specification).

Bertha