[
https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772079#action_12772079
]
Jörn Kottmann commented on UIMA-1647:
-------------------------------------
For me it works if . runUimaClass.sh is replaces with sh
$UIMA_HOME/bin/runUimaClass.sh,
maybe it should be sh "$UIMA_HOME/bin/runUimaClass.sh" to not fail if the
UIMA_HOME contains
spaces.
When the dot notation is used to run runUimaClass.sh it seems to get the
parameter passed which is passed
to deployAsyncService.sh and not the params intended for it in the
deployAsyncService.sh script.
It then fails because it cannot find a class with the name of the deployment
descriptor
in my case: bin/deployAsync.sh descritpor.xml, where "descriptor.xml" is not a
valid class name.
> 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.
