[
https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772871#action_12772871
]
Marshall Schor commented on UIMA-1647:
--------------------------------------
I think you only have to surround substituted values which contain a blank in
certain contexts (which seem to vary on different OS's)
Line 49 error - on my linux, that was a line 46 error, related to the script
fragment:
if [ -e $ACTIVEMQ_HOME ] and I got that to go away by surrounding
$ACTIVEMQ_HOME with double quotes.
The error around the "export" - I didn't see that on SUSE Linux. But I'm
betting that in your OS, the tokenizer is running over the argument following
export after the variable substitution. So, for all exports I enclosed the
next argument xxx=yyyyyyyy in quotes.
It didn't change anything on my Linux test environment. Can you try this in
yours? I committed the change so you can see it.
> 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
> Assignee: Jörn Kottmann
> Priority: Blocker
> Fix For: 2.3, 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.
