com.ibm.etools.iseries.remotebuild.actions
Class ArtifactCleanupAction
java.lang.Object
Action
com.ibm.etools.iseries.remotebuild.actions.ArtifactCleanupAction
public class ArtifactCleanupAction
- extends Action
An ArtifactCleanupAction is instantiated on a iSeries connection and an age.
When run, it cleans up any remote build artifacts found in the home folder
of that connection that are older than the specified age.
This action is meant to be run on a non-UI thread since it sleeps occasionally.
Method Summary |
RBStatus |
getStatus()
|
void |
run()
Cleans up any remote build artifacts older than the specfied age that
are found in the home folders of connections associated with iseries
projects in the workspace. |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Copyright
public static final String Copyright
- See Also:
- Constant Field Values
ArtifactCleanupAction
public ArtifactCleanupAction(int age,
int fileMax)
- Create a new ArtifactCleanupAction.
- Parameters:
age
- the minimum number of days that an artifact has aged to be eligible
for deletion.fileMax
- the maximum number of files to clean up in this action
run
public void run()
- Cleans up any remote build artifacts older than the specfied age that
are found in the home folders of connections associated with iseries
projects in the workspace. Connections that are not in "connected" state
are skipped.
This action may be run on a non-UI thread.
This action may be rerun.
getStatus
public RBStatus getStatus()
- Returns:
- the status of the last run of this action. If the action has never
been run the status is
null
.
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.