Community
Participate
Working Groups
Now that java 1.5 is becoming more widespread as an authoring language for plug-ins we should give the ability to RCP app authors to specify the minimum level of JRE required in the product file. The value will result in setting the osgi.requiredJavaVersion property in the config.ini file. In short what it comes down to? A text field in the product editor where people can specify the JRE level required and the generation of the appropriate property in the config.ini.
does osgi.requiredJavaVersion take a version number or an EE?
It takes a VM version number like 1.4, 1.4.2, 1.5, etc.
shouldn't it take reall EE names lke J2SE-1.4?
It would be a real shame if it didn't take an EE
EE is not enough. For example eclipse needs 1.4.2 and will not run properly on 1.4.1.
Adam, here is another one for you if you desire. A checkbox and a text value here sounds good. I would put it in the Launching tab, in the Java Runtime Environment section.
Moving off PDE. Back to inbox.
Bartosz, this another interesting one possibly.
I leave and all my work goes to Bartosz, eh? Make PDE proud!
Tom, what are the valid values of osgi.requiredJavaVersion? And Why is Pascal bent on this :)?
Hey Tom, can you comment about that osgi requiredJava version capability?
osgi.requiredJavaVersion is used to compare against the value of the java.version property supplied by the VM. Unfortunately this value (java.version) is not well spec'ed by the VM specification. We assume the value is a '.' separated value (e.g. 1.4.1, 1.4.2, 1.5 etc.) If PDE was to support this then I suggest you support values of major.minor[.micro] Is it worth it for PDE to support this config property? Unfortunately the runtime has way too many options, trying to expose every nob and button to the user will be confusing.
*** Bug 218608 has been marked as a duplicate of this bug. ***
Closing as WONTFIX. This is not an option product developers are clamoring for. Please reopen if you are interested in contributing a fix.
