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] Resolved: (UIMA-1647) Scripts fail to call runUimaClass.sh
Date Tue, 03 Nov 2009 18:21:32 GMT

     [ https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marshall Schor resolved UIMA-1647.
----------------------------------

    Resolution: Fixed

This problem is specific to some shells, like the dash shell (which Ubuntu has /bin/sh ->
dash) and the FreeBSD shell - their impl of the "." command do not support parameter passing.

Fixed by following Burn's suggestion: deleting the "." altogether, and *exporting* any variables
that we want the inner scripts to "see".

This has potentially a slight backwards compatibility issue:  if previous *user-written* scripts
used the "." approach, without exporting
variables, to include our scripts, these would need to be updated.  But I don't think that's
common practice.

Assigning to Jörn - please confirm on your systems when you get a chance :-)

> 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.


Mime
View raw message