 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Java Forum / First Aid / July 2009JRE install fails
Hello, We want to install a specific JRE version in our product. I try to use a silent install for our setup: start /w jre-6u14-windows-i586.exe /s INSTALLDIR=c:\... REBOOT=Suppress STATIC=1 However, it seems that it doesn't work if the same JRE version is already installed on the machine... Do you have an idea how to make this work? Thanks,  SignaturePatrick On Wed, 01 Jul 2009 09:40:27 +0200, Patrick <peuimporte@quelquepart.fr> wrote, quoted or indirectly quoted someone who said : >Do you have an idea how to make this work? One way to do it is to use an installer. See http://mindprod.com/jgloss/installer.html You might cook up a micro-installer, a tiny C program that just checks if Java already installed, and execs as needed. SignatureRoedy Green Canadian Mind Products http://mindprod.com "Deer hunting would be fine sport, if only the deer had guns." ~ William S. Gilbert of Gilbert and Sullivan Le 01/07/2009 10:40, Roedy Green a écrit : > On Wed, 01 Jul 2009 09:40:27 +0200, Patrick > <peuimporte@quelquepart.fr> wrote, quoted or indirectly quoted someone [quoted text clipped - 7 lines] > You might cook up a micro-installer, a tiny C program that just checks > if Java already installed, and execs as needed. I already intended to use an installer, but this doesn't solve the problem: what to do if the same JRE version is already installed? Can we force the installation anyway? (We want that our JRE stays inside our product, not to rely on an external JRE that could be removed.) Thanks, SignaturePatrick Just include the JRE folder in your installer. If you want to use a certain JRE only with your product, you don't need to do a full installation including registry entries etc. Le 01/07/2009 11:12, Daniel Hohenberger a écrit : > Just include the JRE folder in your installer. If you want to use a > certain JRE only with your product, you don't need to do a full > installation including registry entries etc. It would indeed be much simpler, but are you sure it could not cause other problems? - I had the feeling that the JRE installer did some compilations and optimisations on the target installation machine. Maybe it would not work as well if copied on another machine? - Maybe there are legal issues? SignaturePatrick > Le 01/07/2009 11:12, Daniel Hohenberger a écrit : >> Just include the JRE folder in your installer. If you want to use a [quoted text clipped - 3 lines] > It would indeed be much simpler, but are you sure it could not cause > other problems? Fewer than doing system maintenance on someone else's machine. > - I had the feeling that the JRE installer did some compilations and > optimisations on the target installation machine. Maybe it would not > work as well if copied on another machine? Wrong. > - Maybe there are legal issues? Fewer than doing system maintenance on someone else's machine. Read the license agreement on the JRE. SignatureLew > Le 01/07/2009 10:40, Roedy Green a écrit : >> On Wed, 01 Jul 2009 09:40:27 +0200, Patrick [quoted text clipped - 12 lines] > force the installation anyway? (We want that our JRE stays inside our > product, not to rely on an external JRE that could be removed.) So this is for a customer machine, one for whose maintenance you are not responsible? Then installing a whole new JRE is irresponsible. It's their machine, not yours. Instead, extract (not install) a JRE into a subdirectory of your product's installation directory and use relative paths to invoke it. SignatureLew On Wed, 01 Jul 2009 11:07:58 +0200, Patrick <peuimporte@quelquepart.fr> wrote, quoted or indirectly quoted someone who said : >I already intended to use an installer, but this doesn't solve the >problem: what to do if the same JRE version is already installed? Can we >force the installation anyway? (We want that our JRE stays inside our >product, not to rely on an external JRE that could be removed.) Some products install a JVM and don't register it along with the other JVMs. This means the other Java apps don't see it. It also means to uninstall it, you uninstall your app. The user cannot uninstall it separately. That is referred to as a "private" JVM. The disadvantage is you get all manner of duplicate JVMs. The advantage is the app sticks with the JVM that brung it. It has been too long since I fiddled with commercial installers to tell how to get the feature. I was underwhelmed by all of them, and decided some day I would eventually have to write my own. SignatureRoedy Green Canadian Mind Products http://mindprod.com "Deer hunting would be fine sport, if only the deer had guns." ~ William S. Gilbert of Gilbert and Sullivan On Wed, 01 Jul 2009 09:30:17 -0700, Roedy Green <see_website@mindprod.com.invalid> wrote, quoted or indirectly quoted someone who said : > That is referred to as a "private" JVM. see http://mindprod.com/jgloss/installer.html#PRIVATE SignatureRoedy Green Canadian Mind Products http://mindprod.com "Deer hunting would be fine sport, if only the deer had guns." ~ William S. Gilbert of Gilbert and Sullivan Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2010 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.