Bug 194362 - [packaging] all plugins (bundles) should have manifest.mf
Summary: [packaging] all plugins (bundles) should have manifest.mf
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.5.3   Edit
Assignee: Andrew Eisenberg CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-26 01:01 EDT by David Williams CLA
Modified: 2008-07-08 11:59 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2007-06-26 01:01:57 EDT 
I've noticed this plugin does not have a manifest.mf file. 
Not sure why, seems easy to do, and having one prevents it 
having to be created "on the fly" on initial startup. 

org.eclipse.aspectj 

Plus, not having one prevents it from being "indexed" as an OSGi bundle, 
which is how I happened to notice it.
Comment 1 Matt Chapman CLA 2007-06-26 04:43:02 EDT 
(In reply to comment #0)
> I've noticed this plugin does not have a manifest.mf file. 
> Not sure why, seems easy to do, and having one prevents it 
> having to be created "on the fly" on initial startup. 

Not sure why either, I guess it never seemed to need one.

I will see about adding one, but as the lack doesn't appear to be a show stopper for Europa, I'll do it after the release.
Comment 2 Andrew Clement CLA 2008-06-13 14:12:47 EDT 
add a manifest if we still dont have one!
Comment 3 Andrew Eisenberg CLA 2008-07-08 11:58:37 EDT 
This is done.
Comment 4 Andrew Clement CLA 2008-07-08 11:59:35 EDT 
closing as Andrew indicates this isnt a problem any more.