Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348241 - org.eclipse.rap.rwt.source misses BREE header
Summary: org.eclipse.rap.rwt.source misses BREE header
Status: CLOSED WONTFIX
Alias: None
Product: RAP
Classification: RT
Component: Releng (show other bugs)
Version: 1.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-03 12:28 EDT by Ralf Sternberg CLA
Modified: 2016-01-26 05:46 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 Ralf Sternberg CLA 2011-06-03 12:28:55 EDT 
It seems that the source bundle for org.eclipse.rap.rwt is generated without the Bundle-RequiredExecutionEnvironment header.
Comment 1 Markus Knauer CLA 2012-12-06 10:06:00 EST 
This hasn't changed with RAP 2.0 and the migration to the Tycho builds. Then I checked all generated source bundles from the Eclipse Platform build S-4.3M3-201210312000 and they do not contain the Bundle-RequiredExecutionEnvironment either. From my point of view it would be fine to close this bug as wontfix.
Comment 2 Ralf Sternberg CLA 2012-12-06 10:17:29 EST 
(In reply to comment #1)
> This hasn't changed with RAP 2.0 and the migration to the Tycho builds. Then
> I checked all generated source bundles from the Eclipse Platform build
> S-4.3M3-201210312000 and they do not contain the
> Bundle-RequiredExecutionEnvironment either. From my point of view it would
> be fine to close this bug as wontfix.

If it's clear that the problem is not on our side, I'm fine with closing this bug. However, I think it's not correct behavior, as the imported project will be missing information. Maybe we should ask/report this to ... Tycho?
Comment 3 Ivan Furnadjiev CLA 2016-01-26 05:46:53 EST 
(In reply to comment #1)
> From my point of view it would be fine to close this bug as wontfix.

(In reply to comment #2)
> If it's clear that the problem is not on our side, I'm fine with closing this bug. 

As this is very old bug I will close it as suggested as WONTFIX.