Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 255822 - Wrong types and methods used in org.eclipse.help
Summary: Wrong types and methods used in org.eclipse.help
Status: RESOLVED DUPLICATE of bug 256921
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-ua-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-19 11:12 EST by Olivier Thomann CLA
Modified: 2009-03-27 19:21 EDT (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 Olivier Thomann CLA 2008-11-19 11:12:54 EST 
That bundle is supposed to be Foundation 1.0 compliant according to the 3.4
plan. Maybe this has changed for 3.5.
The EEs defined for this project are:
Bundle-RequiredExecutionEnvironment: J2SE-1.4,
 CDC-1.0/Foundation-1.0,
 J2SE-1.3

And for the compilation, pde.build ends up taking the first execution
environment which is 1.4. If pde.build would take the latest execution
environment, it would not compile.

The bundle execution environment should be changed to 1.4 or some type
references should be removed.

Here is the list of possible problematic references found by the new validation
from api tooling:
The type java.util.LinkedHashSet referenced in org.eclipse.help.internal.util.ProductPreferences is not defined in bundle's required execution environment: J2SE-1.3
The constructor LinkedHashSet(Collection) referenced in org.eclipse.help.internal.util.ProductPreferences is not defined in bundle's required execution environment: J2SE-1.3

java.util.LinkedHashSet has been added in 1.4.
Since 1.3 fails, the other execution environment Foundation 1.0 is not even checked.
Comment 1 Chris Goldthorpe CLA 2009-03-27 19:21:29 EDT 

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