Restore equals() and hashCode() methods for DockerConnection.

104b675 removed equals() and hashCode() because they originally took the
connection name into account. As a result, changing the connection name
would generate new refresh threads since the map that stored these used
the connection as the key.

The equals() and hashCode() methods should be determined by the host
path / certificates used and not on any given name. Delegate to the
TCP/UNIX implementation of IDockerConnectionSetting and remove calls to
their parent (BaseConnectionSettings) which checks the name. Also ensure
that duplicate connections aren't added.

Change-Id: I9800ff12b51cd3f44e95ebefdef1579b0bdbdffc
Reviewed-on: https://git.eclipse.org/r/77550
Tested-by: Hudson CI
Reviewed-by: Roland Grunberg <rgrunber@redhat.com>
6 files changed
tree: 7f1b4ac010a7ce3a3dfae1de518b30201e20300b
  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!