commit | 99a3796d83a3957b6a3cd68bcf10f5526e4a7a9d | [log] [tgz] |
---|---|---|
author | Roberto Oliveira <rdutra@linux.vnet.ibm.com> | Thu Oct 06 13:02:07 2016 -0300 |
committer | Roberto Oliveira <rdutra@linux.vnet.ibm.com> | Thu Oct 06 15:56:22 2016 -0400 |
tree | f9825dc19195278fb0c0f7862146ce9c4a559fa7 | |
parent | f7804b3a331df8f7aef861539a8d18293526b06e [diff] |
proxy: fix in RuntimeProcessFactory#whichCommand method After executing the which command in the machine, the method was checking if the process error stream was not null and if it was not null, it was supposing that the command was not installed. This checking can be error phrone because you can get any errors from the machine bash or things like that and it will suppose that the command is not installed. As the method already check the process input stream to get the command path (or empty if not found), I am removing the error stream checking. Change-Id: If454b06596fc2915f034493440f18f5d8cbe8796 Signed-off-by: Roberto Oliveira <rdutra@linux.vnet.ibm.com> Reviewed-on: https://git.eclipse.org/r/82657 Tested-by: Hudson CI Reviewed-by: Wainer dos Santos Moschetta <wainersm@linux.vnet.ibm.com>
Thanks for your interest in this project.
The Linux Tools project aims to bring a full-featured C and C++ IDE to Linux developers. We build on the source editing and debugging features of the CDT and integrate popular native development tools such as the GNU Autotools, Valgrind, OProfile, RPM, SystemTap, GCov, GProf, LTTng, etc. Current projects include LTTng trace viewers and analyzers, an RPM .spec editor, Autotools build integration, a Valgrind heap usage analysis tool, and OProfile call profiling tools. The project also provides a place for Linux distributions to collaboratively overcome issues surrounding distribution packaging of Eclipse technology. The project produces both best practices and tools related to packaging. One of our features is a source archive of the Eclipse SDK that can be used by all Linux distributions building and distributing it.
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
Contact the project developers via the project's “dev” list.
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!