Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #260283 +++ The proposal is to just remove JRE and None as an option and have a checkbox for EE selection. This will solve a problem where in PDE Build ignores the JRE section currently as it doesn't know where to copy the JRE bits from. If you have an EE, PDE Build can infer the location as it's specified in the master build.properties
Andrew, if you just have an EE listed for product definitions, I assume you should be able to get the location of the JRE and bundle it? Currently, PDE UI accomplishes this via root files and would simplify code on our end.
We don't know the locations of any JREs. The properties you are referring to for the EEs are classpaths and are not necessarily a full JRE for any particular platform. Even in the case where the classpath does happen to be inside a JRE, we have no idea what platform that JRE is for and still have nothing for any other platforms.
Can we add something to PDE Build where you can specify the location of a JRE for a given EE? That would seem to solve the problem.
Created attachment 121877 [details] org.eclipse.pde.ui.patch A patch to simplify the JRE section of the product editor. Now people only have the EE as an option to select from. The migration issue of what happens to someone who specified a JRE before will be tackled in another bug.
Created attachment 121878 [details] mylyn/context/zip
done. > 20090107