Community
Participate
Working Groups
From bug 176787 > Would the wizard be able to check for a compliant JVM (1.4.2 or above - or has 3.3 upped that to 1.5?) > and/or specify it in eclipse.ini? It is a very common problem on the newcomers newsgroup > that they are not using a good JVM > Or perhaps the installer itself would not work without that same JVM...? There are two questions here... (1) what JVM is required to run installer (2) what JVM is required to run deployed code So (1) The installer requires JVM 1.4 or better to run, but we may be able to reduce this to JVM 1.3 if necessary. What is our minimum JVM for the installer to run? JVM 1.3? 1.4? (2) When the installer is running, we can check for an applicable JVM and warn the user if they need something more. Is this what you are thinking?
(In reply to comment #0) > (1) The installer requires JVM 1.4 or better to run, but we may be able to > reduce this to JVM 1.3 if necessary. What is our minimum JVM for the installer > to run? JVM 1.3? 1.4? > > (2) When the installer is running, we can check for an applicable JVM and warn > the user if they need something more. Is this what you are thinking? I don't think it makes any sense to invest time/effort in making the installer run in anything less than Eclipse itself requires. If it did, all it would do would tell the user they need a later JVM. What happens now if the installer can't find a good JVM? If the installer does the min JVM check up front in preparation and can provide a friendly response when the requirement is not met, then I guess it does not need to check again during the actual install. But if Eclipse moves up to, for example, require Java 5, would it be better to have the installer require the same or let it run and then warn about the problem during install? I'm not sure...
Closing as WONTFIX. There are no plans to work on the installer. (The packages itself contain a -Dosgi.requiredJavaVersion=1.5 in the eclipse.ini which opens a error dialog if someone tries to start them with a 1.4 JVM.)
