> - The JAVA_HOME env variable is no longer needed (instead, it looks in the
> registry to get the JDK path).
The problem with this is that when you install the JDK you end up with two
JREs. So Java developers may have JAVA_HOME pointed at c:\jdk1.3.1 (say) and
the registry is pointing at c:\program files\JavaSoft\JRE\1.3.1 (or
similar). This means that adding jars to c:\jdk1.3.1\jre\lib\ext would not
work if tomcat is looking for the JRE through the registry.
I would prefer to see a check for JAVA_HOME and if that's not set then look
in the registry. Or, if both the registry and JAVA_HOME is set, offer the
user the choice. If you've already done this then ignore my ramblings!
Kevin Jones
DevelopMentor
www.develop.com
> -----Original Message-----
> From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
> Sent: 17 July 2001 06:10
> To: [EMAIL PROTECTED]
> Subject: New Tomcat 4 installer nightly
>
>
> Hi,
>
> I did lots of updates to the installer script, and the result is available
> here :
> http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly/jakart
> a-tomcat-4
> .0-20010716.exe
>
> Changes from the first installer include :
> - The JAVA_HOME env variable is no longer needed (instead, it looks in the
> registry to get the JDK path).
> - Includes the latest security fix.
> - Added links to edit the config files.
> - Won't delete the configuration and logs when uninstalling
> (unless you ask
> the uninstaller to do so).
> - Won't overwrite the configuration files if some are present. That makes
> upgrading to a new build easier (but more work will be done in that area).
> - Fix the minimum installation.
>
> I think it's solid enough so that we can release the upcoming
> 4.0b6 packaged
> with it.
>
> Remy
>
