Bug 535115 - Invalid OSGi manifest error: 'Bundle-Version' header is required
Summary: Invalid OSGi manifest error: 'Bundle-Version' header is required
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7.3   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-25 09:25 EDT by Duch Bechlegor CLA
Modified: 2024-04-30 13:01 EDT (History)
3 users (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 Duch Bechlegor CLA 2018-05-25 09:25:36 EDT 
'Bundle-Version' is not a required OSGi header. So why Eclipse reports that it is required? How to turn off this error (in Eclipse 4.4 such errors are not reported).
Comment 1 Eclipse Genie CLA 2020-05-15 06:56:58 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 2 Alexander Fedorov CLA 2020-05-17 01:40:56 EDT 
I don't think the error is invalid as "Bundle-Version" is required for OSGi R4, i.e. for bundles with "Bundle-ManifestVersion" >=2

I think this ticket should be either closed or reformulated to support OSGi R3 bundle manifest validation.

@Vikas WDYT?
Comment 3 Vikas Chandra CLA 2020-05-19 12:43:53 EDT 
The code that flags this as error is present since 2006

79668dc3fa697276ee359f75a854f6433fcdb4ad ( via bug 125416)

>>How to turn off this error

Probably a preference could be useful

>>@Vikas WDYT?

Let's check with Thomas.
Comment 4 Vikas Chandra CLA 2020-05-19 12:45:12 EDT 
Hi Thomas, can you give your views on comment#0. Also see comment#2 and comment#3.
Comment 5 Thomas Watson CLA 2020-05-19 13:12:37 EDT 
(In reply to Vikas Chandra from comment #4)
> Hi Thomas, can you give your views on comment#0. Also see comment#2 and
> comment#3.

Bundle-Version is not a required header at any OSGi spec version.  For OSGi R4 there was a change that the Bundle-Version header (if specified) must be able to be parsed into an osgi Version object.  Prior to OSGi R4 the Bundle-Version header had no specified format and could be anything the manifest author wanted.

If the Bundle-Version header is not specified then the default is to have the bundle versioned at 0.0.0
Comment 6 Eclipse Genie CLA 2022-05-10 13:45:35 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 7 Eclipse Genie CLA 2024-04-30 13:01:27 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.