There are tons of messages floating around describing a variety of problems. It seems that the most problematic platform in this respect is Microsoft Windows, and Linux or Mac OSX are both much less tricky.
Using Android monkeyrunner from Eclipse is one of the all-time most popular post in this blog. Clearly, this indicates that the setup is not as straightforward as it should be, so I decided to post a detailed configuration that has been tested and is the one I mostly use to develop tools like AndroidViewClient, which has been described in latests posts like monkeyrunner: interacting with the Views.
After this brief introduction we are ready to start, firstly my Eclipse Helios configuration:
- Android DDMS 16.0.1.v201112150204-238534
- Android Development Tools 16.0.1.v201112150204-238534
- Android Hierarchy Viewer 16.0.1.v201112150204-238534
- Android Traceview 16.0.1.v201112150204-238534
- AspectJ Development Tools 2.1.3.e36x-20110622-1300
- Cross References tool (XRef) 2.1.3.e36x-20110622-1300
- EclEmma Java Code Coverage 220.127.116.11112281951
- Eclipse EGit 18.104.22.168112221803-r
- Eclipse IDE for Java Developers 22.214.171.12410301-1807
- Eclipse JGit 126.96.36.199112221803-r
- Eclipse Weaving Service Feature 2.1.3.e36x-20110622-1300
- Equinox Weaving SDK 1.0.0.v20100421-79--EVVFNFFsFc
- m2e - Maven Integration for Eclipse 188.8.131.5210804-1717
- m2e - slf4j over logback logging (Optional) 184.108.40.20610804-1717
- PyDev for Eclipse 220.127.116.111062419
- Pydev Mylyn Integration 0.3.0
Following this configuration we will be using one of the AndroidViewClient's example: browser-open-url.py. This is showing its run configuration.