commit | b18690415eb8d3040fc797b5ea7b4f5cf27f4a2a | [log] [tgz] |
---|---|---|
author | Roland Grunberg <rgrunber@redhat.com> | Tue Jun 13 15:43:12 2017 -0400 |
committer | Roland Grunberg <rgrunber@redhat.com> | Tue Jun 13 19:13:16 2017 -0400 |
tree | 76d20a42cdddd893856d0c3e3d96ada9783dcc85 | |
parent | 520c8e6ed86ef64f5fd2979a344dee624cb3c8c6 [diff] |
Correct paths when not on Windows and never pass a 'null' port mapping. - UnixFile.convertDOSPathToUnixPath() only needs to be done on Windows - We need to pass an empty String [] rather than a null for port map argument of ContainerLauncher's launch() Change-Id: I376b1f33f6579268e60642f0a40dc4fcf5fe340d Reviewed-on: https://git.eclipse.org/r/99278 Tested-by: Hudson CI Reviewed-by: Roland Grunberg <rgrunber@redhat.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!