Package | Description |
---|---|
com.jayway.android.robotium.remotecontrol.install | |
com.jayway.android.robotium.remotecontrol.solo | |
org.safs.android.auto.lib | |
org.safs.sockets.android |
Modifier and Type | Field and Description |
---|---|
(package private) static AndroidTools |
SilentInstaller.androidtool |
Modifier and Type | Field and Description |
---|---|
protected static AndroidTools |
Solo.androidsdk
static android sdk tool to the one appropriate for the OS (Windows or Unix).
|
static AndroidTools |
SoloRemoteControl.sdk |
Modifier and Type | Field and Description |
---|---|
protected static AndroidTools |
DUtilities.androidsdk
static android sdk tool to the one appropriate for the OS (Windows or Unix).
|
Modifier and Type | Method and Description |
---|---|
static AndroidTools |
AndroidTools.get()
TODO Do we need to keep this tool as a singleton?
If different users call
ConsoleTool.setToolHome(String) to set different tool-path, problem!!!But on one machine, it is rarely that user has different path for one tool. |
static AndroidTools |
DUtilities.getAndroidTools(java.lang.String androidToolHome)
Set our static android sdk tool to the one appropriate for the OS (Windows or Unix).
The routine does nothing if the appropriate sdk instance is already set. For the sdk's tool home, it firstly try to set it to parameter 'androidToolHome' If androidToolHome is not a valid home path: it will try to get it from the 'VM properties' ANDROID_HOME_SYS_PROP or from 'systeme environment' ANDROID_HOME_ENV_VAR or from 'systeme environment' ANDROID_SDK_ENV_VAR |
Modifier and Type | Field and Description |
---|---|
(package private) static AndroidTools |
DroidSocketProtocol.tools |
Copyright © SAS Institute. All Rights Reserved.