headers
Marshall Schor (JIRA | 2 Nov 16:10
Picon
Favicon

[jira] Assigned: (UIMA-1647) Scripts fail to call runUimaClass.sh


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

Marshall Schor reassigned UIMA-1647:
------------------------------------

    Assignee: Marshall Schor

> 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:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor (JIRA | 2 Nov 18:02
Picon
Favicon

[jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh


    [
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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jörn Kottmann (JIRA | 2 Nov 19:56
Picon
Favicon

[jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh


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

Jörn Kottmann commented on UIMA-1647:
-------------------------------------

I can do testing on Ubuntu and OS X.

> 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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor (JIRA | 2 Nov 23:00
Picon
Favicon

[jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh


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

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

I did some testing on linux - and found that using the "dot" command seems to work properly - any parameters
passed on the command line starting with the "." are delivered to the inner script correctly.  Also,
variables set (but not exported) I believe get delivered (by definition - that's what the dot does
differently from starting a new shell).

I am changing 

. runUimaClass.sh .....

to

. "$UIMA_HOME/bin/runUimaClass.sh" ....

which I think will fix the problems reported above, and have some scripts which set (but do not export)
variables have those variables "visible" to the runUimaClass script.

Thanks for offering to do testing - I'll certainly take you up on that :-)  

> Scripts fail to call runUimaClass.sh 
> -------------------------------------
>
>                 Key: UIMA-1647
(Continue reading)

Permalink | Reply | 3 comments |
headers
Jörn Kottmann (JIRA | 2 Nov 23:10
Picon
Favicon

[jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh


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

Jörn Kottmann commented on UIMA-1647:
-------------------------------------

I tried . "$UIMA_HOME/bin/runUimaClass.sh" and did not work in the case of deployAsyncService.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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor (JIRA | 2 Nov 23:40
Picon
Favicon

[jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh


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

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

I found some cases where arguments which could contain blanks were not properly quoted, especially for
*nix.  I'm fixing those too...  A good test would be to install into a directory whose name contains a blank
(both on windows and *nix) and see if the scripts still work.

> 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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor (JIRA | 2 Nov 23:48
Picon
Favicon

[jira] Resolved: (UIMA-1647) Scripts fail to call runUimaClass.sh


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

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

       Resolution: Fixed
    Fix Version/s: 2.3
         Assignee: Jörn Kottmann  (was: Marshall Schor)

I tested this on linux - trying the documentAnalyzer script as a test.   Seems to work.  Please test other
scripts in other environments :-)

> 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
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jörn Kottmann (JIRA | 3 Nov 01:50
Picon
Favicon

[jira] Reopened: (UIMA-1647) Scripts fail to call runUimaClass.sh


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

Jörn Kottmann reopened UIMA-1647:
---------------------------------

It does not work in the case UIMA_HOME contains a white space, I get this error when
trying to start cpeGui.sh:
joern <at> karkand:~/uima test/apache-uima$ bin/cpeGui.sh
[: 49: /home/joern/uima: unexpected operator
export: 65: test/apache-uima//uimacpp/bin:/home/joern/uima: bad variable name

Do we have to surround all UIMA_XXX variables with quotations marks ? 

> 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
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor (JIRA | 3 Nov 05:10
Picon
Favicon

[jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh


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

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

I think you only have to surround substituted values which contain a blank in certain contexts (which seem
to vary on different OS's)

Line 49  error - on my linux, that was a line 46 error, related to the script fragment:
if [ -e $ACTIVEMQ_HOME ] and I got that to go away by surrounding $ACTIVEMQ_HOME with double quotes.

The error around the "export" - I didn't see that on SUSE Linux.  But I'm betting that in your OS, the tokenizer
is running over the argument following export after the variable substitution.  So, for all exports I
enclosed the next argument xxx=yyyyyyyy  in quotes.  

It didn't change anything on my Linux test environment.   Can you try this in yours?  I committed the change so
you can see it.

> 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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Burn Lewis | 3 Nov 05:55
Picon

Re: [jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh

Marshall,

Since we don't set any variables before calling runUimaClass I don't think
we need the "." --- all that matters is we get the environment and "sh" or
no prefix will do that.

-Burn.

On Mon, Nov 2, 2009 at 6:00 PM, Marshall Schor (JIRA) <
uima-dev@...> wrote:

>
>    [
> https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772713#action_12772713]
>
> Marshall Schor commented on UIMA-1647:
> --------------------------------------
>
> I did some testing on linux - and found that using the "dot" command seems
> to work properly - any parameters passed on the command line starting with
> the "." are delivered to the inner script correctly.  Also, variables set
> (but not exported) I believe get delivered (by definition - that's what the
> dot does differently from starting a new shell).
>
> I am changing
>
> . runUimaClass.sh .....
>
> to
>
(Continue reading)

Permalink | Reply | 2 comments |

Gmane