Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329415 - 'org.eclipse.equinox.util' specifies BREE which I cannot find
Summary: 'org.eclipse.equinox.util' specifies BREE which I cannot find
Status: RESOLVED WORKSFORME
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Compendium (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.compendium-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-04 03:47 EDT by Dani Megert CLA
Modified: 2010-11-04 12:32 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2010-11-04 03:47:17 EDT
'org.eclipse.equinox.util' specifies 'OSGi/Minimum-1.1' as BREE. I can find other JREs in /org.eclipse.sdk-feature/libs but not this one.

==> where does the releng build fetch that JRE and how can I get hold on such a JRE, so that I can get rid of the following build path error on 'org.eclipse.equinox.util':

Build path specifies execution environment OSGi/Minimum-1.1. There are no JREs installed in the workspace that are strictly compatible with this environment.
Comment 1 Thomas Watson CLA 2010-11-04 09:05:20 EDT
OSGi/Minimum-1.1 is a subset of J2SE 1.4 and Foundation 1.1.  My workspace shows all Java SE installations as being compatible.  Are you saying when you go to the preferences for execution environments none of you installed Java SE environments show up as compatible?
Comment 2 Dani Megert CLA 2010-11-04 09:34:28 EDT
(In reply to comment #1)
> OSGi/Minimum-1.1 is a subset of J2SE 1.4 and Foundation 1.1.  My workspace
> shows all Java SE installations as being compatible.  Are you saying when you
> go to the preferences for execution environments none of you installed Java SE
> environments show up as compatible?
Compatible is not the same as being strictly compatible: go to some other EE and you will see bold entries for the exact matches. Also, simply import the project as binary project and you will see the warning (I have set that to error in my workspace).
Comment 3 Dani Megert CLA 2010-11-04 09:42:00 EDT
Why do I have this set as error? Because using a compatible super-set is dangerous because one might easily use methods which will not be available at runtime when using the specified BREE.
Comment 4 Thomas Watson CLA 2010-11-04 09:56:30 EDT
In the build I think we use Foundation 1.1 jar for the profile or we use the profile jars provided by org.eclipse.osgi/osgi at http://dev.eclipse.org/viewsvn/index.cgi/org.eclipse.equinox/framework/bundles/org.eclipse.osgi/osgi/?root=RT_Project

That has a number of ee jars and ee files you can use to configure the ee into Eclipse.  I also install the EE profiles for API tooling that will catch errors if your reference API outside of your specified BREEs.
Comment 5 Dani Megert CLA 2010-11-04 12:32:28 EDT
> the profile jars provided by org.eclipse.osgi/osgi at
> http://dev.eclipse.org/viewsvn/index.cgi/org.eclipse.equinox/framework/bundles
> /org.eclipse.osgi/osgi/?root=RT_Project

That worked for me, thanks!