Overridden function that performs a checkout (resynchronize) operation against an MKS Source Project
This function ignores the scmVerion and recursive arguments passed into this function as while there is
a suitable equivalent to checkout/resynchronize by label/revision, it doesn't make sense for the way
Maven seems to want to execute this command.
Since we can't arbitrarily apply the same start and end revisions to all files in the sandbox,
this command will be adapted to show differences between the local version and the repository
Even though this command is supported via the MKS JAVA API, since at this time we really don't
know what the SCM plugin is looking to get in return for this command, we're simply going to
run this command via the CLI and return the output verbatim
MKS Integrity implementation for Maven's AbstractBranchCommand
For a normal and variant configuration, a fresh checkpoint is executed
prior to creating a Development Path (branch).
MKS Integrity implementation for Maven's AbstractChangeLogCommand
Currently there is a limitation in the 'si rlog' command where changes
can't be limited to a normal/variant/build configuration.
MKS Integrity implementation for Maven's AbstractCheckInCommand
The check-in command will also drop any files that are missing from the working directory
MKS Integrity implementation for Maven's AbstractCheckOutCommand
The Checkout command will create a fresh sandbox in the checkoutDirectory
Since, Maven deletes the prior checkout folder, this command will check
for a prior sandbox in the checkout directory and if a sandbox was found,
then the command will resynchronize the sandbox.
MKS Integrity implementation for Maven's AbstractDiffCommand
Since MKS Integrity doesn't have a notion of arbitrarily differencing
by a revision across the sandbox, this command will difference the
current Sandbox working file against the server version.
MKS Integrity implementation for Maven's AbstractEditCommand
Since it does not make sense to lock all files in the Sandbox,
this command will make all of the working files writable in the Sandbox
MKS Integrity implementation for Maven's AbstractExportCommand
Since the IntegrityCheckoutCommand creates a fresh Sandbox in the checkoutDirectory,
it does not make sense for the IntegrityExportCommand to essentially do the same thing.
MKS Integrity implementation of Maven's AbstractLockCommand
This command will execute a 'si lock' on the specified member,
which assumes the user has a valid Sandbox to work with.
MKS Integrity implementation of Maven's AbstractLoginCommand
This command will execute a 'si login' followed by a 'si viewproject'
to prepare the subsequent commands that will be executed for a maven goal.
MKS Integrity implementation of Maven's AbstractMkdirCommand
This command will execute an 'si createsubproject' for the relative path
represented in the fileSet.getFileList().iterator().next() entry.
MKS Integrity implementation for Maven's AbstractStatusCommand
This command will execute a 'si viewsandbox' and report on all
changed and dropped working files.
MKS Integrity implementation of Maven's AbstractTagCommand
This command will execute a 'si checkpoint' command using a groovy
script for evaluating the tag (label) name
MKS Integrity implementation of Maven's AbstractUnEditCommand
This command will execute a 'si revert' command which will revert
any modified working files back to their server versions
IntegrityUnlockCommand constructor requires a filename argument to be supplied for its execution
This avoids having to run the unlock command across the entire Sandbox.
MKS Integrity implementation of Maven's AbstractUpdateCommand
This command will execute a 'si resync' to synchronize the sandbox with the server revisions.
This class represents an MKS Integrity Source File
It needs the Member Name (relative path to pj), Full Member Path, Project Configuration Path, Revision,
Project's Root Path, and the current Workspace directory (to compute the working file path) for its
instantiation.