You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@uima.apache.org by Katherine Enderling <ka...@cognia.com> on 2007/05/04 17:00:14 UTC

Exception using ibmUimaToApacheUima.sh

I'm trying to run ibmUimaToApacheUima.sh but it's getting the following
exception:

Migrating your files...
Exception in thread "main" java.lang.NullPointerException
        at 
org.apache.uima.tools.migration.IbmUimaToApacheUima.replaceInAllFiles(IbmUim
aToApacheUima.java:158)
        at 
org.apache.uima.tools.migration.IbmUimaToApacheUima.main(IbmUimaToApacheUima
.java:106)

I'm giving it one input parameter of the absolute path to a directory.
Until this point my UIMA setup seems to have worked since I can run the
documentAnalyzer tool.

Do you know what's causing this?
Thanks!
Katherine

Re: Exception using ibmUimaToApacheUima.sh

Posted by Adam Lally <al...@alum.rpi.edu>.

On 5/4/07, Hannes Meyer | RCAG <hm...@rc.ag> wrote:
> Hi,
>
> check this issue:
> https://issues.apache.org/jira/browse/UIMA-393
>

Right... there is a bug in the script, the workaround is to edit
ibmUimaToApacheUima.sh and change the %1 to $1.

-Adam

AW: Exception using ibmUimaToApacheUima.sh

Posted by Hannes Meyer | RCAG <hm...@rc.ag>.

Hi,

check this issue:
https://issues.apache.org/jira/browse/UIMA-393

Bests
Hannes

-----Ursprüngliche Nachricht-----
Von: Katherine Enderling
[mailto:katherine_enderling@cognia.com] 
Gesendet: Freitag, 4. Mai 2007 17:00
An: uima-user@incubator.apache.org
Betreff: Exception using ibmUimaToApacheUima.sh

I'm trying to run ibmUimaToApacheUima.sh but it's getting
the following
exception:

Migrating your files...
Exception in thread "main" java.lang.NullPointerException
        at
org.apache.uima.tools.migration.IbmUimaToApacheUima.replaceI
nAllFiles(IbmUim
aToApacheUima.java:158)
        at
org.apache.uima.tools.migration.IbmUimaToApacheUima.main(Ibm
UimaToApacheUima
.java:106)

I'm giving it one input parameter of the absolute path to a
directory.
Until this point my UIMA setup seems to have worked since I
can run the documentAnalyzer tool.

Do you know what's causing this?
Thanks!
Katherine