[
https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773462#action_12773462
]
Marshall Schor commented on UIMA-1647:
--------------------------------------
The last svn commit didn't appear in this Jira (SVN was down when I made the
commit, 832657). This commit removed extra setting of the UIMA_CLASSPATH
(including the wrong separator char). I didn't add a check for CATALINA_HOME -
if that is not set, the classes needed for running SOAP with deployTool will
have to be provided by the user - if they don't provide it, they will get the
can't find org.apache.axis.client.AdminClient. This is how it worked before,
too.
> 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.
