Bug 508405 - Fix copy to container to support stopped containers

- fix ContainerCopyToCommandHandler to issue cause of any
  DockerException to the user
- fix CopyToContainer wizard to pass whether the container is
  stopped or not
- fix CopyToContainerPage to override the destination controls
  when stopped to just add a single Text widget and no browse
  button
- fix ContainerDirectoryDialog invocation to include a message
  which contains the container name in it
- fix CopyFromContainer as well with regards to displaying the
  cause of any DockerException rather than the top-level message
- fix the copyfromcommand handler enablement to be if the container
  status is not unknown

Change-Id: Ibd620c615e5bfa6ee7fcb28e1f8afc3ac318e296
Reviewed-on: https://git.eclipse.org/r/85991
Tested-by: Hudson CI
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
8 files changed
tree: 9a187bb667b125757cb283fba921f38f26d12565
  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!