executable that ships with Teamprise Explorer. However, it is possible to bypass the launcher executable when running Teamprise Explorer. This allows certain kinds of errors to be captured more easily. You may be asked to do this in order to troubleshoot

executable to your shell's execution path. Because the command line shells are different for each platform, the instructions are platform specific. Prerequisites Make sure you have installed the Teamprise Command Line Client. For installation instructions, follow the link to the referenced

executable after being written to disk (files are normally not made executable; directories are). This attributes is only supported by Teamprise on Unix platforms (including Mac OS X) and may not be applied to directories. Teamprise will turn on the execute

executable (for example, TeampriseExplorer.exe on Windows). One of the things this launcher program does is to locate a Java Runtime Environment (JRE) for Teamprise Explorer. The native launcher normally selects the proper JRE to use and requires no additional configuration

executable. Details The eclipse launcher executable (for example, eclipse.exe on Windows) is responsible for launching a JVM process to host Eclipse. The parameters for increasing the available memory differ from JVM to JVM. The instructions given below are valid for Sun's JVMs

executable must simply be in your execution path), Teamprise recommends that it be configured for consistent operation. Note: On Unix platforms TEAMPRISE_CLC_HOME must be defined if a symbolic link pointing to the CLC executable is used to invoke

executed. To do this add the following dependencies: ... org.apache.maven.plugins maven-scm-plugin org.apache.maven.scm maven-scm-provider-tfs 1.0.0 org.apache.maven.plugins maven-release-plugin org.apache.maven.scm maven-scm-provider-tfs 1.0.0 ... Usage of the SCM Provider The TFS SCM Provider can be invoked

executable from the command line, with additional command line arguments. The `-vmargs` argument is required to specify arguments to the Java Virtual Machine. The `-Xmx` argument will specify the memory size. For example, to increase to 1 GB of memory

execution in the CLC. If you have defined a check-in policy on a team project that cannot be run in the CLC, check-ins made with the CLC will fail. You can override this failure using the -override option

executable. When the Teamprise Explorer is initially loaded, a dialog will appear prompting for your Teamprise license key. If you haven't purchased a license key, the option to obtain a demo license or purchase a license will be present