Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326726

Summary:	useradmin bundle missing manifest-version property
Product:	[Eclipse Project] Equinox	Reporter:	Wim Jongman <wim.jongman>
Component:	Compendium	Assignee:	equinox.compendium-inbox <equinox.compendium-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	tjwatson
Version:	unspecified
Target Milestone:	3.7 M4
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Wim Jongman

2010-09-30 19:17:19 EDT

Manifest.mf should contain this line:

Manifest-Version: 1.0

Comment 1 Wim Jongman

2010-11-09 17:22:53 EST

ping!

Comment 2 Thomas Watson

2010-11-10 09:52:45 EST

Done for 3.7.  I am a bit confused why this is causing you issues.  Our build process uses the jar ant task which inserts the Manifest-Version header for us.  Our built jars of the useradmin bundle do have the Manifest-Version header.

Comment 3 Wim Jongman

2010-11-10 10:05:34 EST

Hi Thomas,

Thanks. I don't know why. Buckminster checks out the bundle from CVS and then fails because of the missing property. It should be in the manifest right? Otherwise I can investigate why this is causing bucky so much problems.

Comment 4 Thomas Watson

2010-11-10 11:20:02 EST

It should be there only to be consistent with our other manifests, but from my POV we should not be required to have the Manifest-Version header in our source files for the manifest.  This is added automatically by the jar utilities during a build.

Anyway, I added it because there is no harm in doing so, it makes it consistent with our other manifests, and most importantly, it helps you ;-)

Comment 5 Wim Jongman

2010-11-10 11:43:28 EST

Thanks, that is very much appreciated!