Amazon Mechanical Turk Command Line Tools Can't Run From Any Directory
The Amazon Mechanical Turk (AMT) Command Line Tools (CLT) 1.3.0 claims that you can run it from any directory if you just set the MTURK_CMD_HOME environment variable. However, that's not true (as least it's not true on Windows). If you set the environment variable and try to run the tools, you will get the following error message:
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/cli/BasicParser
I found the reason for it is because of bugs in the "invoke.cmd" that is distributed with AMT CLT. In this batch script, it references the current directory variable (%CD%) rather than the MTURK_CMD_HOME variable.
I fixed the problem in the attached "invoke.cmd" script. The license for this script is covered under then same Amazon Software License ( http://aws.amazon.com/asl ).
With this fix, you will get another error message:
There was a problem reading your properties file from mturk.properties
It seems like a Java class file in the AMT CLT is also not reading the MTURK_CMD_HOME variable. Instead, it is probably looking for the configuration in the current working directory. But at least you can resolve that by moving the "mturk.properties" file around.
Did your message disappear? Read the Forums FAQ.
Spam Control | * indicates required field
TrackBack only accepted from WebSite-X Suite web sites. Do not submit TrackBacks from other sites.
No TrackBacks yet. TrackBack can be used to link this thread to your weblog, or link your weblog to this thread. In addition, TrackBack can be used as a form of remote commenting. Rather than posting the comment directly on this thread, you can posts it on your own weblog. Then have your weblog sends a TrackBack ping to the TrackBack URL, so that your post would show up here.
Messages, files, and images copyright by respective owners.
29 Users Online
Copyright © 1996 - 2019. All Rights Reserved.