uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thilo Götz <twgo...@gmx.de>
Subject Re: Problems installing UIMA on W7
Date Tue, 16 Nov 2010 16:07:17 GMT
On 11/16/2010 16:44, Erik-Lân Do Dinh wrote:
> Hello everyone,
> I want to install UIMA on a Windows 7 (x64) machine, Java version is 1.6 (x86).
> I installed UIMA according to http://uima.apache.org/doc-uima-examples.html,
> double checked all path entries and install path. Now, when I try to run
> "adjustExamplePaths.bat", it outputs an error message and stops.
> The message:
> ------
> C:\Program Files (x86)\apache-uima\bin>setlocal
> "\Java\jdk1.6.0_22\bin\java)" kann syntaktisch an dieser Stelle nicht verarbeite
> t werden.
> C:\Program Files (x86)\apache-uima\bin>if "C:\Program Files (x86)\Java\jdk1.6.0_
> 22"=="" (set UIMA_JAVA_CALL=java) else (set UIMA_JAVA_CALL=C:\Program Files (x86
> )\Java\jdk1.6.0_22\bin\java)
> ------
> The first part says: "\Java\jdk1.6.0_22\bin\java)" cannot be processed
> syntactically at this place.
> The second part is just an output of the line 
> if "%JAVA_HOME%"=="" (set UIMA_JAVA_CALL=java) else (set
> from adjustExamplePaths.bat with %JAVA_HOME% replaced by its value.
> Now, if I just replace that last line with
> set UIMA_JAVA_CALL=%JAVA_HOME%\bin\java
> the script runs ok. But when I want to try out documentAnalyzer.bat, the same
> error ("cannot be processed ...") occurs, now in runUimaClass.bat (which is
> called by documentAnalyzer.bat). I can fix that too, but then another error
> crops up, etc.
> I also tried putting the apache-uima-directoy directly into C: (changed the env
> vars of course), but the same errors keep happening.

I think the problem is not the UIMA install path, but the Java install
path.  It chokes on the closing paren of the (x86) part (great idea, MS).

I don't have the time to try this now, but try replacing
if "%JAVA_HOME%"=="" (set UIMA_JAVA_CALL=java) else (set


if "%JAVA_HOME%"=="" (set UIMA_JAVA_CALL=java) else set

Let us know if this works, and we'll fix it.


> Has anybody experienced the same problem and maybe has found a solution? Or can
> anyone see where I made a mistake which causes all the hassle?
> Help would be much appreciated, thanks for reading this
> Erik-Lân Do Dinh

View raw message