com.ibm.etools.iseries.remotebuild.actions
Class WorkWithCompileCommandsAction
java.lang.Object
Action
com.ibm.etools.iseries.remotebuild.actions.RBAction
com.ibm.etools.iseries.remotebuild.actions.ResourceAction
com.ibm.etools.iseries.remotebuild.actions.WorkWithCompileCommandsAction
public class WorkWithCompileCommandsAction
- extends ResourceAction
This class wraps the WorkWithCompileCommands action provided by the base RSE support.
Constructor Summary |
WorkWithCompileCommandsAction(Shell shell,
List resources)
Creates a new WorkWithCompileCommandsAction that can then be run to bring up
the WWCC dialog. |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
WorkWithCompileCommandsAction
public WorkWithCompileCommandsAction(Shell shell,
List resources)
throws IllegalArgumentException
- Creates a new WorkWithCompileCommandsAction that can then be run to bring up
the WWCC dialog.
- Parameters:
shell
- The shell that will be the parent to the dialogresources
- The list of RBResources that will be used to determine the initial value for the dialog.
All resources must be from the same project. If all resources are the members with the same source
type then the dialog should be positioned to that source type in the default private profile, otherwise
it will be positioned to the first source type of the default private profile.
- Throws:
IllegalArgumentException
- if the resource list is empty,
if the list contains objects that are not RBResources,
if any resource in the list does not belong to a project,
or if the resources span projects.
run
public void run()
getText
public String getText()
getImageDescriptor
public ImageDescriptor getImageDescriptor()
Copyright © 2011 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.