Software Deployment

Let me guess....you're using Wise Package Studio? With the option set to add registry data to the advertising tables?

This is WPS/JRE being...odd. When Wise goes to get COM information from the JRE DLLs, some widget somewhere tells it that the JRE version required is x.y.x_ab and, because the machine has x.y.w_de, it throws the bottle out of the pram. I have never been motivated to find out exactly who spoils the party because a) I don't have the time and b) I have a simple work-around.

The work-around I've always used is a self-authored script to fool the machine into believing that it has the requisite version. You can do it long-hand by exporting the relevant registry data (HKLM\Software\JavaSoft\[version] - it'll be obvious when you open the 'JavaSoft' key), editing the resulting .REG and then importing the edited data. The most effective w/a, though, is to pre-install the JRE it wants before capturing.

So you are saying to add a registry data during Setup Capture to fool that the Java plug-in is installed. But wont it create any problem if that plug-in is actually installed later?

Add the registry before to the machine so it will not be included during capture.
You don't want that registry info in the package.

So you are saying to add a registry data during Setup Capture to fool that the Java plug-in is installed.No. Install the JRE you have and then fudge the registry entries before starting your capture so that when WPS goes to get the COM information, it believes that the required JRE version is present.

But wont it create any problem if that plug-in is actually installed later?All you're interested in is having WPS able to get the COM information from the DLLs. As for the app itself, I have yet to come across any apps that fail because they were built with, say 1.4.2_02 but the machine they're installed on has, say, 1.4.1_01, or even 1.5.1_10.