Bug 563412 - Port Settings inconsistently saved/restored for Docker Run

- add new IRunDockerImageLaunchConfigurationConstants.UNUSED_PORTS
- modify ImageRun.getDockerHostConfig() to take a list argument
  that will be modified to contain all unselected ports
- fix ExposedPortModel.fromString() method to not include the
  slash separator as part of the type
- modify LaunchConfigurationUtils.createRunImageLaunchConfiguration
  method to accept new unused ports list argument
- modify RunDockerImageLaunchConfigurationDelegate to pass an
  empty unused ports list to RunImageCommandHandler.runImage()
- modify RunImageCommandHandler.execute() to use new API for
  getting host config and setting unused ports list
- modify RunImagePortsTab.initializeFrom() method to get unused ports
  from launch configuration
- fix Docker ui tests to pass empty unused ports list
- remove checkAllElements() in ImageRunSelectionPage and let
  selection be determined dynamically from settings
- fix ImageRunSelectionPage.setDefaultValues() to restore
  unused ports

Change-Id: I0eda891c30334604cfe59511e553448540ac1f88
Reviewed-on: https://git.eclipse.org/r/163348
Tested-by: Linux Tools Bot <linuxtools-bot@eclipse.org>
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
10 files changed
tree: c57f11ca17a2b46b0e8ae8d6b4f4375e319cfcfb
  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. .project
  19. pom.xml
  20. 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!