Bug 533649 - Minor bug fixes for Run Docker Image launch configuration

* Fix RunImagePortsTab port type setting serialization. When
ExposedPortModel host address is null (unset), properly serialize it as
empty string instead.
* Fix RunImagePortsTab host address setting deserialization. Update
ContainerPortDialog port type to "tcp" to match deserialization format
used in ExposedPortModel.createPortModel()
* Fix RunImageEnvironmentTab bug which always wipe all environment
variables when tab is activated. Use setEnvironmentVariables() instead
of clear and add so that the UI only triggers one model change event
that does not accidentally wipe all environment variables.
* Minor UI layout adjustments in tabs to fill up the remaining real
estate.

Change-Id: Ia182ea304a88c0191f621977a642d21e289b9251
Signed-off-by: Chin Huat Ang <chin.huat.ang@intel.com>
Reviewed-on: https://git.eclipse.org/r/121384
Tested-by: CI Bot
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
7 files changed
tree: f6b795fce47cbd1b2775f31a918055426c143caf
  1. changelog/
  2. containers/
  3. gcov/
  4. gprof/
  5. javadocs/
  6. libhover/
  7. lttng/
  8. man/
  9. mylyn/
  10. oprofile/
  11. perf/
  12. profiling/
  13. releng/
  14. rpm/
  15. systemtap/
  16. vagrant/
  17. valgrind/
  18. .gitignore
  19. .project
  20. pom.xml
  21. 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!