cdt/launch/org.eclipse.cdt.docker.launcher/plugin.properties

###############################################################################
#  Copyright (c) 2015 Red Hat Inc. and others.
#  All rights reserved. This program and the accompanying materials
#  are made available under the terms of the Eclipse Public License v1.0
#  which accompanies this distribution, and is available at
#  http://www.eclipse.org/legal/epl-v10.html
#
#  Contributors:
#      Red Hat Inc. - initial API and implementation
###############################################################################
Plugin.name=C/C++ Container Launch Plug-in
Plugin.vendor=Eclipse CDT
Delegate.name=C/C++ Container Launcher
Delegate.desc=This launcher runs C/C++ applications in a specified Docker Container.  The Container \
must be set-up to supply the C/C++ application what it needs to run.
LaunchConfigurationType.name=C/C++ Container Launcher
Shortcut.label=C/C++ Container Application
DockerLaunchPreferencePage.name=Docker Container Launch
ContainerCommandLauncherFactory.name=Container Command Launcher Factory
Container.settings=Container Settings
ContainerBuild.property.enablement=Container Build Enablement
ContainerBuild.property.connection=Container Build Connection
ContainerBuild.property.image=Container Build Image
Add Docker launching support - use the new docker tooling plug-ins to launch and debug CDT C/C++ applications in docker containers Change-Id: I30689255a3443ce6d49f937f5e2506d86452915b 2015-04-24 19:38:08 -04:00			`###############################################################################`
			`# Copyright (c) 2015 Red Hat Inc. and others.`
			`# All rights reserved. This program and the accompanying materials`
			`# are made available under the terms of the Eclipse Public License v1.0`
			`# which accompanies this distribution, and is available at`
			`# http://www.eclipse.org/legal/epl-v10.html`
			`#`
			`# Contributors:`
			`# Red Hat Inc. - initial API and implementation`
			`###############################################################################`
			`Plugin.name=C/C++ Container Launch Plug-in`
			`Plugin.vendor=Eclipse CDT`
			`Delegate.name=C/C++ Container Launcher`
			`Delegate.desc=This launcher runs C/C++ applications in a specified Docker Container. The Container \`
			`must be set-up to supply the C/C++ application what it needs to run.`
			`LaunchConfigurationType.name=C/C++ Container Launcher`
			`Shortcut.label=C/C++ Container Application`
			`DockerLaunchPreferencePage.name=Docker Container Launch`
Bug 513589 - Add support to build CDT projects in a Docker Container - add IOptionalBuildObjectPropertiesContainer interface to use for objects that supply optional build properties - add new IOptionalBuildProperties interface that defines optional build properties donated by external plug-ins - add new - change IConfiguration to an IOptionalBuildObjectPropertiesContainer - change IManagedProject to be an IOptionalBuildObjectPropertiesContainer - fix ProcessClosure to ensure that readers are not null before accessing them - fix Container launch delegate to look at project optional build properties for active configuration to fetch connection and image info and use said info to find a matching launch or create a new one - have Container launch delegate use the image name as part of the launch config name - have Container launch short-cut also use the project's optional build properties for the active config to get connection and image information before any defaulting - change AutotoolsNewMarkerGenerator to store the command launcher as an ICommandLauncher - add new CommandLauncherFactory extension to cdt.core that allows plug-ins to specify a CommandLauncherFactory that will return an ICommandLauncher based on the project - add macros for new extension to CCorePlugin - add new CommandLauncherFactoryManager class that loads CommandLauncherFactory extensions and is used to give an ICommandLauncher wrapper that will go through the list of CommandLauncherFactory extensions until one returns non-null ICommandLauncher - add code to RemoteCommandLauncher so it will use the CommandLauncherFactoryManager to get the local launcher - also change RemoteCommandLauncher to check at execution time whether the command is local and in that case use the local command launcher - add new ICommandLauncherFactory interface - add new ContainerCommandLauncher to launch - add new ContainerCommandLauncherFactory class for returning a ContainerCommandLauncher instance to launch commands in a Docker Container - change MakeBuilder to use CommandLauncherFactoryManager to get its ICommandLauncher - change CommandBuilder to use CommandLauncherFactoryManager too - ditto for Builder and AbstractBuiltinSpecsDetector and ExternalToolInvoker - change Configuration to load/store optional build properties as well as return the properties to get/set - ditto for MultiConfiguration - change ManagedProject to implement IOptionalBuildOptionProperties interface - ditto for ProjectType - create new OptionalBuildProperties class to store optional build properties for a configuration - bump cdt.managedbuilder.core to 8.5.0 - bump cdt.docker.launcher to 1.1.0 - use CommandLauncherFactory extension to define ContainerCommandLauncherFactory - add optional ContainerPropertyTab which allows the end-user to optionally choose to build a C/C++ project in a Container and specify the connection/image to use Change-Id: Id4d202d5eeb0dd52e528a45bf44d3e386f67376d 2017-02-09 18:43:05 -05:00			`ContainerCommandLauncherFactory.name=Container Command Launcher Factory`
			`Container.settings=Container Settings`
			`ContainerBuild.property.enablement=Container Build Enablement`
			`ContainerBuild.property.connection=Container Build Connection`
			`ContainerBuild.property.image=Container Build Image`