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

Bug 344763

Summary:	PDE should support case insensitive manifest headers
Product:	[Eclipse Project] PDE	Reporter:	Curtis Windatt <curtis.windatt.public>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	pwebster, remy.suen, tjwatson
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug
Bug Depends on:	344767
Bug Blocks:	288862

Description Curtis Windatt

2011-05-04 16:23:45 EDT

There are many places in PDE where we load a manifest file into maps then lookup the various headers.  However, we do all lookups against the framework's string constants.  Manifest headers are supposed to be case-insensitive, but these map lookups will fail if the user is using all lower case headers (some generated manifests come out this way).

We have a workaround for syntax highlighting in the manifest editor, see bug 151172.  The same problem exists in build, see bug 61653

For a case that is directly impacting users see bug 288862.

Comment 1 Curtis Windatt

2011-05-04 16:24:39 EDT

If we can come up with a straightforward code snippet, it could easily be applied to the many places we work with the headers, but this won't happen in 3.7.

Comment 2 Curtis Windatt

2011-05-04 17:20:39 EDT

There is the possibility of getting a better parseBundleManifest() implementation from equinox in 3.8.  We could move all of the calls to the new method to get case-insensitive manifest checking.  See bug 344767.

Comment 3 Curtis Windatt

2012-02-28 15:11:54 EST

It isn't clear if bug 344767 will get fixed for Juno, but PDE resources are severely restricted so I am dropping this item.

Comment 4 Eclipse Genie

2019-09-06 16:52:29 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.