[
https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772099#action_12772099
]
Jörn Kottmann commented on UIMA-1647:
-------------------------------------
Yes UIMA_HOME/bin is not in my path, so thats why it cannot find
runUimaClass.sh, but I think its common not to have UIMA_HOME/bin in the path,
right ?
Then we have to add the check for UIMA_HOME to every shell script ... maybe the
other way around would have been better, e.g. having one script to call other
scripts like run.sh COMMAND.
> Scripts fail to call runUimaClass.sh
> -------------------------------------
>
> Key: UIMA-1647
> URL: https://issues.apache.org/jira/browse/UIMA-1647
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Environment: Ubuntu Server 8.10, Java 1.6
> Reporter: Jörn Kottmann
> Priority: Blocker
> Fix For: 2.3AS
>
>
> Executing deployAsyncService.sh fails with the following error message:
> .: 28: runUimaClass.sh: not found
> deployAsyncService.sh calls runUimaClass.sh with ". runUimaClass.sh ...",
> in an older version this script called setUimaClassPath.sh, but that was
> done with the absolute path:
> . "$UIMA_HOME/bin/setUimaClassPath.sh"
> I suggest that we change all our .sh scripts to use the absolute path like
> it was done before for at least the deployAsyncService.sh script.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
