[
https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773510#action_12773510
]
Jörn Kottmann commented on UIMA-1647:
-------------------------------------
We could also do it like this:
"$UIMA_JAVA_CALL" -DVNS_HOST=$VNS_HOST -DVNS_PORT=$VNS_PORT
"-Duima.home=$UIMA_HOME" "-Duima.datapath=$UIMA_DATAPATH"
"-Djava.util.logging.config.file=$UIMA_LOGGER_CONFIG_FILE"
"-Duima.tools.cvd.manpath=$UIMA_CVDMAN" $UIMA_JVM_OPTS
-DUimaBootstrapSuppressClassPathDisplay
-Dorg.apache.uima.jarpath="$UIMA_CLASSPATH" -jar
"$UIMA_HOME/lib/uimaj-bootstrap.jar" $*
And then change UIMA_CVDMAN to only include the path, in case its empty the
property is empty or not set (don't know the exact behavior).
> 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.
