commit | f874f011ddbb3c841aa5881470599ef5ee23846b | [log] [tgz] |
---|---|---|
author | Jeff Johnston <jjohnstn@redhat.com> | Thu Aug 22 16:50:59 2019 -0400 |
committer | Jeff Johnston <jjohnstn@redhat.com> | Thu Aug 22 22:11:32 2019 -0400 |
tree | 935bfa0f3b93ad3345f0c9b10c5edef8933c6c0b | |
parent | ca989ebd9c0049dd327462149fc264cb6c66e2f5 [diff] |
Bug 550348 - Java container support shows image id rather than repo tag - fix ContainerLauncher.launch() method to check if the image name to be shown matches the image id and if so, get the DockerImage to figure out the first repo tag and use it instead Change-Id: Ifc35e9efffc6aaab64bd3c077212550a604d9017 Reviewed-on: https://git.eclipse.org/r/148164 Tested-by: Linux Tools Bot <linuxtools-bot@eclipse.org> Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
Thanks for your interest in this project.
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.
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
Contact the project developers via the project's “dev” list.
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!