uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh
Date Mon, 02 Nov 2009 17:02:59 GMT

    [ https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772560#action_12772560
] 

Marshall Schor commented on UIMA-1647:
--------------------------------------

The "other way around" mentioned by Jörn is used by some other launchers - for instance,
Hadoop.  We could add it, but I think we have to restore the "UIMA_HOME being set" test to
the other scripts, for backwards compatibility.  That's what I'm planning to do, along with
changing the "." command to sh (for .sh)

> 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: Marshall Schor
>            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.


Mime
View raw message