Community
Participate
Working Groups
We have... Bundle-RequiredExecutionEnvironment: CDC-1.0/Foundation-1.0, J2SE-1.2 ...in the MANIFEST.MF file, but we have... <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.2"/> ...in the project's .classpath file. Isn't the .classpath entry supposed to point at the first entry of the BREE?
Are you seeing a particular problem? In the case of Orbit bundles, most do not have actual source that we are compiling so the .classpath setting is not really used. You might be seeing a warning about an exact match JRE not being available. Unless something else is going on you should be able to "Update classpath" and resolve the situation.
(In reply to comment #1) > You might be seeing a warning about an exact match JRE not being > available. The warning in question is... The JRE container on the classpath is not a perfect match to the 'CDC-1.0/Foundation-1.0' execution environment ...but I do have a perfect match for CDC-1.0/Foundation-1.0 in my workspace settings, it's just that the .classpath wants J2SE-1.2, which is why I filed this bug. If both the .classpath and BREE wanted J2SE-1.2, I wouldn't have a problem with this. All I'm asking is for the .classpath file to point at one EE and the BREE's first entry to be the same. I know I can correct it locally and I understand that this is not a real problem since Orbit is usually holding binaries but I'd just like to feel more at ease by not seeing "any" warnings on libraries I have no control over when I do a CVS checkout. :)
Unless someone sees a problem, updating the classpath seems to make sense here. I do recall seeing a related PDE bug report talking about how when you change the BREE the classpath is not always updated. Seems related here.
+1. Jeff, are you running an older build and able to release this change? Unfortunately I am running the latest and am running into bug 220811. Note that the map file doesn't have to be updated since the .classpath file isn't included in the builds. Thanks.
I have updated the classpath for both v3.0.1 and v3.1.0. Closing.
I noticed that after updating the 3.1.0 plugin it no longer exports its classes. It seems that this line got accidentally lost from the .classpath file? <classpathentry exported="true" kind="lib" path="" sourcepath="source-bundle"/>
Fixed. Thanks.
