Remote Systems
v6.4.1

com.ibm.etools.systems.localfilesubsys.impl
Class LocalCandidateCommand

java.lang.Object
  extended bycom.ibm.etools.systems.subsystems.impl.CandidateCommandImpl
      extended bycom.ibm.etools.systems.localfilesubsys.impl.LocalCandidateCommand
All Implemented Interfaces:
IAdaptable, ICandidateCommand, ISystemOutputRemoteTypes

public class LocalCandidateCommand
extends CandidateCommandImpl
implements ICandidateCommand, ISystemOutputRemoteTypes

Represents a local command possibility object


Field Summary
static String copyright
           
 
Fields inherited from class com.ibm.etools.systems.subsystems.impl.CandidateCommandImpl
_description, _imageDescriptor, _name, _path, _type, Copyright
 
Fields inherited from interface com.ibm.etools.systems.subsystems.ICandidateCommand
Copyright
 
Fields inherited from interface com.ibm.etools.systems.commands.ISystemOutputRemoteTypes
TYPE_COMMAND, TYPE_DIRECTORY, TYPE_ENVVAR, TYPE_ENVVAR_LIBPATH, TYPE_ENVVAR_PATH, TYPE_ERROR, TYPE_FILE, TYPE_GREP, TYPE_INFORMATIONAL, TYPE_PROCESS, TYPE_PROMPT, TYPE_WARNING, TYPECATEGORY
 
Constructor Summary
LocalCandidateCommand(File file)
           
 
Methods inherited from class com.ibm.etools.systems.subsystems.impl.CandidateCommandImpl
getAdapter, getDescription, getImageDescriptor, getName, getPath, getType
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 
Methods inherited from interface com.ibm.etools.systems.subsystems.ICandidateCommand
getDescription, getImageDescriptor, getName, getPath, getType
 

Field Detail

copyright

public static final String copyright
See Also:
Constant Field Values
Constructor Detail

LocalCandidateCommand

public LocalCandidateCommand(File file)

Remote Systems
v6.4.1

Copyright © 2005 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.