Bug 336619 - Don't syntax highlight "version" attribute on Require-Bundle headers
Summary: Don't syntax highlight "version" attribute on Require-Bundle headers
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Vikas Chandra CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-08 09:09 EST by John Arthorne CLA
Modified: 2023-09-14 04:04 EDT (History)
1 user (show)

See Also:

Attachments
Screen shot (13.16 KB, image/png)
2011-02-08 09:11 EST, John Arthorne CLA 		no flags Details
View All 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 John Arthorne CLA 2011-02-08 09:09:54 EST 
Build: 4.1 M5


If I have a MANIFEST.MF containing the following:

Require-Bundle: org.eclipse.core.runtime;version="[3.4.0,4.0.0)",

PDE manifest editor will highlight the "version" attribute, which suggests it is a legal value. It is not. The correct attribute is "bundle-version". The syntax highlighter should not highlight "version" as an attribute here.
Comment 1 John Arthorne CLA 2011-02-08 09:11:04 EST 
Created attachment 188518 [details]
Screen shot

In this screen shot, there are two invalid attributes: "version", and "foo". However "version" is highlighted differently than "foo", which implies it is legal.
Comment 2 Eclipse Genie CLA 2019-09-17 00:25:10 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.
Comment 3 Eclipse Genie CLA 2021-09-23 07:26:30 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.
Comment 4 Eclipse Genie CLA 2023-09-14 04:04:36 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.