Google Git
Sign in
eclipse / linuxtools / org.eclipse.linuxtools / 4dd73e287e5e3695b8b6433345c3b00b9a31bdeb
commit4dd73e287e5e3695b8b6433345c3b00b9a31bdeb[log] [tgz]
authorRoland Grunberg <rgrunber@redhat.com>Mon Jun 27 12:50:29 2016 -0400
committerRoland Grunberg <rgrunber@redhat.com>Mon Jun 27 16:48:13 2016 -0400
tree493a925f1dcf4bd9717d0c78641d6a0b3c57e5e0
parent44b657a8887cf8e79c8d912dde53edb4b9df08fc [diff]
Bug 496705: Context menu should reflect correct state after command.

Although property testers get re-triggered, the selection data remains
stale leading to incorrect context menu states (eg. start container is
selectable even after the container has already started). Property
testers should query for fresh container data every time.

Change-Id: I25353b534f23374868d83aaf661ad783d8ff71a7
1 file changed
tree: 493a925f1dcf4bd9717d0c78641d6a0b3c57e5e0
  1. changelog/
  2. containers/
  3. gcov/
  4. gprof/
  5. javadocs/
  6. libhover/
  7. lttng/
  8. man/
  9. oprofile/
  10. perf/
  11. profiling/
  12. releng/
  13. rpm/
  14. systemtap/
  15. vagrant/
  16. valgrind/
  17. .gitignore
  18. pom.xml
  19. README.md
README.md

Contributing to Linux Tools

Thanks for your interest in this project.

Project description:

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.

Developer resources:

Information regarding source code management, builds, coding standards, and more.

Contributor License Agreement:

Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).

Contact:

Contact the project developers via the project's “dev” list.

Search for bugs:

This project uses Bugzilla to track ongoing development and issues.

Create a new bug:

Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!