Bug 224439 - Shouldn't use the Manifest class
Summary: Shouldn't use the Manifest class
Status: RESOLVED DUPLICATE of bug 257242
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.5   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks: 249167
  Show dependency tree
 
Reported: 2008-03-27 14:57 EDT by DJ Houghton CLA
Modified: 2008-12-08 15:48 EST (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 DJ Houghton CLA 2008-03-27 14:57:50 EDT 
There are a couple of cases in our code when we are reading the bundle manifest and we use the Manifest class. Instead, we should be using the OSGi helper method ManifestElement#parseBundleManifest since it only reads as much as it needs, and doesn't try and read through all the signing info in the manifest.

Specifically, FrameworkAdmin and SimpleConfigurator still access this class and should be converted. Note there may be issues w.r.t. having them require an Equinox class. (not available in other frameworks)
Comment 1 DJ Houghton CLA 2008-12-08 15:48:00 EST 

*** This bug has been marked as a duplicate of bug 257242 ***