Show
Ignore:
Timestamp:
07.03.2017 17:10:44 (3 years ago)
Author:
ak19
Message:

1. Bugfix: there was a tab space at the end of an env var assignment that broke setting the JAVA_HOME env. 2. Tested more complicated PATH to java_home, one which had round brackets in the PATH. Corrections to cope with this.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • main/trunk/greenstone3/gs3-setup.bat

    r31467 r31468  
    233233if DEFINED FOUNDJAVAHOME  ( 
    234234    echo *** Using the JAVA_HOME detected at !FOUNDJAVAHOME! 
    235     set JAVA_HOME=!FOUNDJAVAHOME! 
     235    set JAVA_HOME=!FOUNDJAVAHOME!    
    236236    set PATH=!FOUNDJAVAHOME!\bin;!PATH! 
    237237    set RUNJAVA=!FOUNDJAVAHOME!\bin\java.exe 
     
    282282"!RUNJAVA!" -d%bitness% -version 2> nul 
    283283if !ERRORLEVEL! equ 1 ( 
    284     echo *** WARNING: Detected mismatch between the bit-ness of your Greenstone installation ^(%bitness% bit^) 
    285     echo *** and the Java found at %RUNJAVA%. 
     284    echo *** WARNING: Detected mismatch between the bit-ness of your Greenstone installation ^(!bitness! bit^) 
     285    echo *** and the Java found at !RUNJAVA!. 
    286286    echo *** Continuing with this Java anyway: 
    287287    echo *** This will only affect MG/MGPP collections for searching, and GDBM database collections