|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Objectcom.perforce.p4java.impl.generic.core.ServerResource
com.perforce.p4java.impl.mapbased.client.ClientSummary
com.perforce.p4java.impl.mapbased.client.Client
public class Client
Default implementation of the generic parts of an IClient interface.
Note that this version is very much tied to the map-based server implementation, and can (generally) only be used with that server type. This is not an onerous requirement, however, as all IServer objects returned from the ServerFactory are map-based implementations.
Nested Class Summary |
---|
Nested classes/interfaces inherited from interface com.perforce.p4java.client.IClientSummary |
---|
IClientSummary.ClientLineEnd, IClientSummary.IClientOptions, IClientSummary.IClientSubmitOptions |
Field Summary | |
---|---|
static String |
DEFAULT_DESCRIPTION
What a new client created by the newClient method uses as a description if nothing is passed in explicitly. |
static String |
MERGE_END_FROM_REV_KEY
|
static String |
MERGE_START_FROM_REV_KEY
|
static String |
MERGE_TMP_FILENAME_KEY
|
Fields inherited from class com.perforce.p4java.impl.mapbased.client.ClientSummary |
---|
accessed, alternateRoots, description, hostName, lineEnd, name, options, ownerName, root, serverId, stream, streamAtChange, submitOptions, unloaded, updated |
Fields inherited from class com.perforce.p4java.impl.generic.core.ServerResource |
---|
refreshable, server, updateable |
Constructor Summary | |
---|---|
Client()
Default constructor. |
|
Client(IClientSummary clientSummary,
boolean refresh)
Construct a new Client object using the passed-in client summary object as a partial template. |
|
Client(IClientSummary clientSummary,
IServer serverImpl,
boolean refresh)
Construct a new Client object using the passed-in client summary object as a partial template along with the passed-in IServer object. |
|
Client(IServer server)
Note that any IServer object returned by the ServerFactory will work for the serverImpl parameter; if not, a suitable cast exception will be thrown. |
|
Client(IServer serverImpl,
Map<String,Object> map)
Construct a suitable Client object from an IServer and a map returned from the Perforce server. |
|
Client(String name,
Date accessed,
Date updated,
String description,
String hostName,
String ownerName,
String root,
IClientSummary.ClientLineEnd lineEnd,
IClientSummary.IClientOptions options,
IClientSummary.IClientSubmitOptions submitOptions,
List<String> alternateRoots,
IServer serverImpl,
ClientView clientView)
Construct a new Client object from explicit fields. |
|
Client(String name,
Date accessed,
Date updated,
String description,
String hostName,
String ownerName,
String root,
IClientSummary.ClientLineEnd lineEnd,
IClientSummary.IClientOptions options,
IClientSummary.IClientSubmitOptions submitOptions,
List<String> alternateRoots,
IServer serverImpl,
ClientView clientView,
String stream)
Construct a new Client object from explicit fields. |
Method Summary | |
---|---|
List<IFileSpec> |
addFiles(List<IFileSpec> fileSpecs,
AddFilesOptions opts)
Open one or more Perforce client workspace files for adding to the Perforce server. |
List<IFileSpec> |
addFiles(List<IFileSpec> fileSpecs,
boolean noUpdate,
int changeListId,
String fileType,
boolean useWildcards)
Open one or more Perforce client workspace files for adding to the Perforce server. |
void |
complete()
Completing a client calls refresh() and updates the
#isComplete() flag. |
List<IFileSpec> |
copyFiles(IFileSpec fromFile,
IFileSpec toFile,
String branchSpec,
CopyFilesOptions opts)
Schedule resolve and integration actions to make the target file identical to the source file based only on the differences between the two (i.e. |
List<IFileSpec> |
copyFiles(IFileSpec fromFile,
List<IFileSpec> toFiles,
CopyFilesOptions opts)
Copies one set of files (the 'source') into another (the 'target'). |
IChangelist |
createChangelist(IChangelist newChangelist)
Create a new changelist for this Perforce client in the associated Perforce server. |
List<IFileSpec> |
deleteFiles(List<IFileSpec> fileSpecs,
DeleteFilesOptions opts)
Open Perforce client workspace files for deletion from a Perforce depot. |
List<IFileSpec> |
deleteFiles(List<IFileSpec> fileSpecs,
int changeListId,
boolean noUpdate)
Open Perforce client workspace files for deletion from a Perforce depot. |
List<IFileSpec> |
editFiles(List<IFileSpec> fileSpecs,
boolean noUpdate,
boolean bypassClientUpdate,
int changeListId,
String fileType)
Open one or more Perforce client workspace files for editing. |
List<IFileSpec> |
editFiles(List<IFileSpec> fileSpecs,
EditFilesOptions opts)
Open one or more Perforce client workspace files for editing. |
ClientView |
getClientView()
Get the Perforce client view associated with this client, if any. |
List<IFileSpec> |
getDiffFiles(List<IFileSpec> fileSpecs,
GetDiffFilesOptions opts)
Return a list of files that differ in some (arbitrarily complex) way from depot. |
List<IFileSpec> |
getDiffFiles(List<IFileSpec> fileSpecs,
int maxFiles,
boolean diffNonTextFiles,
boolean openedDifferentMissing,
boolean openedForIntegrate,
boolean unopenedMissing,
boolean unopenedDifferent,
boolean unopenedWithStatus,
boolean openedSame)
Return a list of files that differ in some (arbitrarily complex) way from depot. |
IServer |
getServer()
Return the IServer object representing the Perforce server associated with this Perforce client. |
List<IFileSpec> |
haveList(List<IFileSpec> fileSpecs)
Return a list of all Perforce-managed files and versions that the Perforce server believes this Perforce client workspace has as of the latest sync. |
List<IFileSpec> |
integrateFiles(IFileSpec fromFile,
IFileSpec toFile,
String branchSpec,
IntegrateFilesOptions opts)
Integrate ("merge") from one Perforce filespec to another. |
List<IFileSpec> |
integrateFiles(IFileSpec fromFile,
List<IFileSpec> toFiles,
IntegrateFilesOptions opts)
Integrate one set of files (the 'source') into another (the 'target'). |
List<IFileSpec> |
integrateFiles(int changeListId,
boolean showActionsOnly,
IntegrationOptions integOpts,
String branchSpec,
IFileSpec fromFile,
IFileSpec toFile)
Integrate ("merge") from one Perforce filespec to another. |
List<IFileSpec> |
labelSync(List<IFileSpec> fileSpecs,
String labelName,
boolean noUpdate,
boolean addFiles,
boolean deleteFiles)
Perform a label sync operation for this client. |
List<IFileSpec> |
labelSync(List<IFileSpec> fileSpecs,
String labelName,
LabelSyncOptions opts)
Perform a label sync operation for this client. |
List<IFileSpec> |
lockFiles(List<IFileSpec> fileSpecs,
int changeListId)
Lock an opened file against changelist submission. |
List<IFileSpec> |
lockFiles(List<IFileSpec> fileSpecs,
LockFilesOptions opts)
Lock an opened file against changelist submission. |
List<IFileSpec> |
mergeFiles(IFileSpec fromFile,
List<IFileSpec> toFiles,
MergeFilesOptions opts)
Merges changes from one set of files (the 'source') into another (the 'target'). |
static Client |
newClient(IOptionsServer server,
String name,
String description,
String root,
String[] paths)
Convenience method to return a new Client object with certain default values filled in. |
List<IFileSpec> |
openedFiles(List<IFileSpec> fileSpecs,
int maxFiles,
int changeListId)
If one or more Perforce file specs is passed-in, return the opened / locked status of each file (if known) within an IFileSpec object; otherwise return a list of all files known to be open for this Perforce client workspace. |
List<IFileSpec> |
openedFiles(List<IFileSpec> fileSpecs,
OpenedFilesOptions opts)
Return a list of files open for this client, optionally restricted to a specific path and / or changelist. |
List<IFileSpec> |
populateFiles(IFileSpec fromFile,
List<IFileSpec> toFiles,
PopulateFilesOptions opts)
Branches a set of files (the 'source') into another depot location (the 'target') in a single step. |
List<IFileSpec> |
reconcileFiles(List<IFileSpec> fileSpecs,
ReconcileFilesOptions opts)
Open files for add, delete, and/or edit to reconcile client with workspace changes made outside of Perforce. |
void |
refresh()
This method will refresh by getting the complete client model. |
List<IFileSpec> |
reopenFiles(List<IFileSpec> fileSpecs,
int changeListId,
String fileType)
Reopen Perforce files in a new changelist. |
List<IFileSpec> |
reopenFiles(List<IFileSpec> fileSpecs,
ReopenFilesOptions opts)
Reopen Perforce files in a new changelist. |
List<IFileSpec> |
resolvedFiles(List<IFileSpec> fileSpecs,
boolean showBaseRevision)
Return a list of files resolved but not submitted for this client. |
List<IFileSpec> |
resolvedFiles(List<IFileSpec> fileSpecs,
ResolvedFilesOptions opts)
Return a list of files resolved but not submitted for this client. |
IFileSpec |
resolveFile(IFileSpec targetFile,
InputStream sourceStream)
Resolve a file integration by using the contents of the sourceStream InputStream as the resolve result. |
IFileSpec |
resolveFile(IFileSpec targetFile,
InputStream sourceStream,
boolean useTextualMerge,
int startFromRev,
int endFromRev)
Resolve a file integration by using the contents of the sourceStream InputStream as the resolve result. |
List<IFileSpec> |
resolveFilesAuto(List<IFileSpec> fileSpecs,
boolean safeMerge,
boolean acceptTheirs,
boolean acceptYours,
boolean showActionsOnly,
boolean forceResolve)
Automatically resolve the results of a previousPerforce file integration. |
List<IFileSpec> |
resolveFilesAuto(List<IFileSpec> fileSpecs,
ResolveFilesAutoOptions opts)
Automatically resolve the results of a previousPerforce file integration. |
List<IFileSpec> |
revertFiles(List<IFileSpec> fileSpecs,
boolean noUpdate,
int changeListId,
boolean revertOnlyUnchanged,
boolean noRefresh)
Revert a open Perforce client workspace files back to the revision previously synced from the Perforce depot, discarding any pending changelists or integrations that have been made so far. |
List<IFileSpec> |
revertFiles(List<IFileSpec> fileSpecs,
RevertFilesOptions opts)
Revert open Perforce client workspace files back to the revision previously synced from the Perforce depot, discarding any pending changelists or integrations that have been made so far. |
void |
setClientView(ClientView clientView)
Set the Perforce client view associated with this client. |
void |
setServer(IServer server)
Note that this will fail with a class cast exception if the passed-in server is not a mapbased ServerImpl object. |
List<IFileSpec> |
shelveChangelist(IChangelist list)
Shelve the file(s) in a pending changelist. |
List<IFileSpec> |
shelveChangelist(int changelistId,
List<IFileSpec> fileSpecs,
boolean forceUpdate,
boolean replace,
boolean discard)
Update/replace/delete shelved file(s) from a pending changelist. |
List<IFileSpec> |
shelveFiles(List<IFileSpec> fileSpecs,
int changelistId,
ShelveFilesOptions opts)
Shelve files in a changelist. |
List<IFileSpec> |
submitShelvedChangelist(int shelvedChangelistId)
Submit a shelved changelist without transferring files or modifying the workspace. |
List<IFileSpec> |
sync(List<IFileSpec> fileSpecs,
boolean forceUpdate,
boolean noUpdate,
boolean clientBypass,
boolean serverBypass)
Sync a Perforce client workspace against the Perforce server. |
List<IFileSpec> |
sync(List<IFileSpec> fileSpecs,
SyncOptions syncOpts)
Sync a Perforce client workspace against the Perforce server. |
void |
sync(List<IFileSpec> fileSpecs,
SyncOptions syncOpts,
IStreamingCallback callback,
int key)
Sync a Perforce client workspace against the Perforce server. |
List<IFileSpec> |
unlockFiles(List<IFileSpec> fileSpecs,
int changeListId,
boolean force)
Release locked files but leave them open. |
List<IFileSpec> |
unlockFiles(List<IFileSpec> fileSpecs,
UnlockFilesOptions opts)
Release locked files but leave them open. |
List<IFileSpec> |
unshelveChangelist(int shelveChangelistId,
List<IFileSpec> fileSpecs,
int clientChangelistId,
boolean forceOverwrite,
boolean previewOnly)
Unshelve file(s) from a shelved changelist |
List<IFileSpec> |
unshelveFiles(List<IFileSpec> fileSpecs,
int sourceChangelistId,
int targetChangelistId,
UnshelveFilesOptions opts)
Unshelve file(s) from a shelf. |
void |
update()
Update the Perforce server object associated with the underlying P4Java object, if possible. |
void |
update(boolean force)
Force (if true) update the Perforce server object associated with the underlying P4Java object, if possible. |
List<IFileSpec> |
where(List<IFileSpec> fileSpecs)
For each of the passed-in file specs, show how the named file maps through the client view. |
Methods inherited from class com.perforce.p4java.impl.mapbased.client.ClientSummary |
---|
getAccessed, getAlternateRoots, getDescription, getHostName, getLineEnd, getName, getOptions, getOwnerName, getRoot, getServerId, getStream, getStreamAtChange, getSubmitOptions, getUpdated, isStream, isUnloaded, setAccessed, setAlternateRoots, setDescription, setHostName, setLineEnd, setName, setOptions, setOwnerName, setRoot, setServerId, setStream, setStreamAtChange, setSubmitOptions, setUpdated |
Methods inherited from class com.perforce.p4java.impl.generic.core.ServerResource |
---|
canRefresh, canUpdate, setRefreshable, update |
Methods inherited from class java.lang.Object |
---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Methods inherited from interface com.perforce.p4java.client.IClientSummary |
---|
getAccessed, getAlternateRoots, getDescription, getHostName, getLineEnd, getName, getOptions, getOwnerName, getRoot, getServerId, getStream, getStreamAtChange, getSubmitOptions, getUpdated, isStream, isUnloaded, setAccessed, setAlternateRoots, setDescription, setHostName, setLineEnd, setName, setOptions, setOwnerName, setRoot, setServerId, setStream, setStreamAtChange, setSubmitOptions, setUpdated |
Methods inherited from interface com.perforce.p4java.core.IServerResource |
---|
canRefresh, canUpdate, update |
Field Detail |
---|
public static final String MERGE_TMP_FILENAME_KEY
public static final String MERGE_START_FROM_REV_KEY
public static final String MERGE_END_FROM_REV_KEY
public static final String DEFAULT_DESCRIPTION
Constructor Detail |
---|
public Client()
ClientSummary fields are set as noted in the ClientSummary default constructor comments.
public Client(IServer server)
ClientSummary fields are set as noted in the ClientSummary default constructor comments.
server
- an IServer server returned from the server factory.public Client(String name, Date accessed, Date updated, String description, String hostName, String ownerName, String root, IClientSummary.ClientLineEnd lineEnd, IClientSummary.IClientOptions options, IClientSummary.IClientSubmitOptions submitOptions, List<String> alternateRoots, IServer serverImpl, ClientView clientView)
Note that any IServer object returned by the ServerFactory will work for the serverImpl parameter; if not, a suitable cast exception will be thrown.
public Client(String name, Date accessed, Date updated, String description, String hostName, String ownerName, String root, IClientSummary.ClientLineEnd lineEnd, IClientSummary.IClientOptions options, IClientSummary.IClientSubmitOptions submitOptions, List<String> alternateRoots, IServer serverImpl, ClientView clientView, String stream)
Note that any IServer object returned by the ServerFactory will work for the serverImpl parameter; if not, a suitable cast exception will be thrown.
public Client(IServer serverImpl, Map<String,Object> map)
Note that any IServer object returned by the ServerFactory will work for the serverImpl parameter; if not, a suitable cast exception will be thrown.
public Client(IClientSummary clientSummary, boolean refresh) throws ConnectionException, RequestException, AccessException
If summary is null, this is equivalent to calling the default constructor. If clientSummary is not null, and refresh is false, the relevant ClientSummary superclass is initialized by copying the passed-in summary fields. If clientSummary is not null and refresh is true, the Client is constructed by calling refresh() using the clientSummary's name; if refresh is false, the client view will be as for the default constructor.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerpublic Client(IClientSummary clientSummary, IServer serverImpl, boolean refresh) throws ConnectionException, RequestException, AccessException
Note that any IServer object returned by the ServerFactory will work for the serverImpl parameter; if not, a suitable cast exception will be thrown.
If summary is null, this is equivalent to calling the default constructor. If clientSummary is not null, and refresh is false, the relevant ClientSummary superclass is initialized by copying the passed-in summary fields. If clientSummary is not null and refresh is true, the Client is constructed by calling refresh() using the clientSummary's name; if refresh is false, the client view will be as for the default constructor.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerMethod Detail |
---|
public static Client newClient(IOptionsServer server, String name, String description, String root, String[] paths)
Only the fields corresponding to the parameters here can be explicitly set on creation; all others are given defaults that can be changed or added later. These defaults are as given for the default Client and ClientSummary constructors; exceptions include the client's user name, which is set to server.getUserName (which may cause issues later down the line if that wasn't set).
Note that this object is a local object only -- you must subsequently call the server's createClient method to also create it on the server (or use the Factory.createClient convenience method).
Note that this method is pretty simple-minded about client names, paths, etc. -- anything that contains unexpected spaces or weird characters (etc.) may cause it to get confused, in which case you're better off constructing things by hand or pre-massaging parameters yourself.
server
- non-null IOptionsServer to be associated with the client.name
- non-null client name.description
- if not null, the client description field to be used; if null,
DEFAULT_DESCRIPTION will be used as a default.root
- if not null, use this as the new client's root; if null, use the server's
working directory if its getWorkingDirectory method returns non-null,
otherwise use the JVM's current working directory as determine by the
user.dir system property.paths
- if not null, use this as the list of view map depot / client
paths, in the order given, and according to the format in
MapEntry.parseViewMappingString; defaults to a single entry,
"//depot/... //clientname/depot/..." if not given.
public IServer getServer()
IClient
getServer
in interface IClient
IClient.getServer()
public void complete() throws ConnectionException, RequestException, AccessException
refresh()
and updates the
#isComplete()
flag. A no op for the new IClient object.
complete
in class ServerResource
ConnectionException
RequestException
AccessException
refresh()
,
ServerResource.complete()
public void refresh() throws ConnectionException, RequestException, AccessException
refresh
in interface IServerResource
refresh
in class ServerResource
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerServerResource.refresh()
public void update() throws ConnectionException, RequestException, AccessException
IServerResource
The results of calling this method on objects whose canUpdate method returns false are undefined (but will generally result in a UnimplementedError being thrown).
update
in interface IServerResource
update
in class ServerResource
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerServerResource.update()
public void update(boolean force) throws ConnectionException, RequestException, AccessException
IServerResource
Note, in order to force the change it may require super user / admin privileges to work properly. The results of calling this method on objects whose canUpdate method returns false are undefined (but will generally result in a UnimplementedError being thrown).
update
in interface IServerResource
update
in class ServerResource
force
- if true, force the update of the object on the server.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerServerResource.update(boolean)
public ClientView getClientView()
IClient
getClientView
in interface IClient
IClient.getClientView()
public void setClientView(ClientView clientView)
IClient
setClientView
in interface IClient
clientView
- new Perforce client view for the client.IClient.setClientView(com.perforce.p4java.impl.generic.client.ClientView)
public void setServer(IServer server)
setServer
in interface IClient
setServer
in interface IServerResource
setServer
in class ServerResource
server
- ServerImpl server object.IServerResource.setServer(com.perforce.p4java.server.IServer)
public List<IFileSpec> sync(List<IFileSpec> fileSpecs, boolean forceUpdate, boolean noUpdate, boolean clientBypass, boolean serverBypass) throws ConnectionException, RequestException, AccessException
IClient
Note that this method will fail (throw a RequestException) unless the client is the associated IServer object's current client.
sync
in interface IClient
fileSpecs
- files to be synchronized; if empty, synchronize all client files.forceUpdate
- if true, forces resynchronization even if the client already
has the file, and clobbers writable files. This flag doesn't affect
open files. Corresponds to the p4 sync "-f" flag.noUpdate
- causes sync not to update the client workspace, but to
display what normally would be updated. Corresponds to the p4 sync "-n" flag.clientBypass
- bypasses the client file update. It can be used to
make the server believe that a client workspace already has the file.
Corresponds to the p4 sync "-k" flag.serverBypass
- populates the client workspace, but does not update the
server to reflect those updates. Any file that is already synced or
opened will be bypassed with a warning message.
Corresponds to the p4 sync "-p" flag.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerIClient.sync(java.util.List, boolean, boolean, boolean, boolean)
public List<IFileSpec> sync(List<IFileSpec> fileSpecs, SyncOptions syncOpts) throws P4JavaException
IClient
sync
in interface IClient
fileSpecs
- files to be synchronized; if empty, synchronize all client files.syncOpts
- SyncOptions object describing sync options; see SyncOptions comments.
P4JavaException
- if any processing errors occur during exection.IClient.sync(java.util.List, com.perforce.p4java.option.client.SyncOptions)
public void sync(List<IFileSpec> fileSpecs, SyncOptions syncOpts, IStreamingCallback callback, int key) throws P4JavaException
IClient
Note that this method takes an IStreamingCallback parameter, and the results are sent to the user using the IStreamingCallback handleResult method; see the IStreamingCallback Javadoc for details. The payload passed to handleResult is usually the raw map gathered together deep in the RPC protocol layer, and the user is assumed to have the knowledge and technology to be able to parse it and use it.
sync
in interface IClient
fileSpecs
- files to be synchronized; if empty, synchronize all client files.syncOpts
- SyncOptions object describing sync options; see SyncOptions comments.callback
- a non-null IStreamingCallback to be used to process the incoming
results.key
- an opaque integer key that is passed to the IStreamingCallback callback
methods to identify the action as being associated with this specific
call.
P4JavaException
- if any processing errors occur during exection.IClient.sync(java.util.List, com.perforce.p4java.option.client.SyncOptions, com.perforce.p4java.server.callback.IStreamingCallback, int)
public List<IFileSpec> labelSync(List<IFileSpec> fileSpecs, String labelName, boolean noUpdate, boolean addFiles, boolean deleteFiles) throws ConnectionException, RequestException, AccessException
IClient
labelSync
in interface IClient
fileSpecs
- if non-null, the list of files dor this operationlabelName
- non-null name of the label to be sync'dnoUpdate
- if true, just show what would result with the labelsync
rather than actually doing itaddFiles
- if true, add the files in fileSpecs to the labeldeleteFiles
- if true, delete the files in fileSpecs from the label
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerIClient.labelSync(java.util.List, java.lang.String, boolean, boolean, boolean)
public List<IFileSpec> labelSync(List<IFileSpec> fileSpecs, String labelName, LabelSyncOptions opts) throws P4JavaException
IClient
labelSync
in interface IClient
fileSpecs
- if non-null, the list of files for this operationlabelName
- non-null name of the label to be sync'dopts
- possibly-null LabelSyncOptions object describing the
specific options for this call
P4JavaException
- if an error occurs processing this method and its parametersIClient.labelSync(java.util.List, java.lang.String, com.perforce.p4java.option.client.LabelSyncOptions)
public IChangelist createChangelist(IChangelist newChangelist) throws ConnectionException, RequestException, AccessException
IClient
The new changelist is returned if the command is successful; this changelist object will include the new changelist ID.
createChangelist
in interface IClient
newChangelist
- non-null specification for the new changelist; if the
newChangelist's ID is not IChangelist.DEFAULT, it is ignored.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerIClient.createChangelist(com.perforce.p4java.core.IChangelist)
public List<IFileSpec> addFiles(List<IFileSpec> fileSpecs, boolean noUpdate, int changeListId, String fileType, boolean useWildcards) throws ConnectionException, AccessException
IClient
addFiles
in interface IClient
fileSpecs
- non-null list of files to be opened, in Perforce client or
depot or local path format.noUpdate
- if true, don't actually do the open, just return the files that
would have been opened for addition.changeListId
- if positive, the opened files are put into the pending
changelist identified by changeListId; this changelist must have been
previously created. If zero or negative, the file is opened in the 'default'
(unnumbered) changelist.fileType
- if non-null, the files are added as that filetype.
See 'p4 help filetypes' to attempt to make any sense of Perforce file types.useWildcards
- if true, filenames that contain wildcards are permitted.
See the main Perforce documentation for file adding for details.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.addFiles(java.util.List, boolean, int, java.lang.String, boolean)
public List<IFileSpec> addFiles(List<IFileSpec> fileSpecs, AddFilesOptions opts) throws P4JavaException
IClient
addFiles
in interface IClient
fileSpecs
- non-null list of files to be opened, in Perforce client or
depot or local path format.opts
- possibly-null AddFilesOptions object specifying method options.
P4JavaException
- if an error occurs processing this method and its parametersIClient.addFiles(java.util.List, com.perforce.p4java.option.client.AddFilesOptions)
public List<IFileSpec> deleteFiles(List<IFileSpec> fileSpecs, int changeListId, boolean noUpdate) throws ConnectionException, AccessException
IClient
deleteFiles
in interface IClient
fileSpecs
- non-null list of files to be openedchangeListId
- if positive, the opened files are put into the pending
changelist identified by changeListId; this changelist must have been
previously created. If zero or negative, the file is opened in the 'default'
(unnumbered) changelist.noUpdate
- if true, don't actually do the open, just return the files that
would have been opened for deletion.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.deleteFiles(java.util.List, int, boolean)
public List<IFileSpec> deleteFiles(List<IFileSpec> fileSpecs, DeleteFilesOptions opts) throws P4JavaException
IClient
deleteFiles
in interface IClient
fileSpecs
- non-null list of files to be openedopts
- possibly-null DeleteFilesOptions object specifying method options.
P4JavaException
- if an error occurs processing this method and its parametersIClient.deleteFiles(java.util.List, com.perforce.p4java.option.client.DeleteFilesOptions)
public List<IFileSpec> editFiles(List<IFileSpec> fileSpecs, boolean noUpdate, boolean bypassClientUpdate, int changeListId, String fileType) throws RequestException, ConnectionException, AccessException
IClient
editFiles
in interface IClient
fileSpecs
- non-null list of files to be opened, in Perforce client or
depot or local path format.noUpdate
- if true, don't actually do the open, just return the files that
would have been opened for edit.bypassClientUpdate
- if true, the edit bypasses any client file update.
Equivalent to the new 2009.2 and later "-k" option. If set true with
a Perforce server earlier than 2009.2, will produce a suitable
RequestException. Note: this option can cause havoc if you don't
use care...changeListId
- if positive, the opened files are put into the pending
changelist identified by changeListId; this changelist must have been
previously created. If zero or negative, the file is opened in the 'default'
(unnumbered) changelist.fileType
- if non-null, the file is opened as that filetype.
Otherwise, the filetype of the previous revision is reused.
If the filetype given is a partial filetype, that partial
filetype is combined with the previous revision's filetype.
See 'p4 help filetypes' to attempt to make any sense of this..
RequestException
- if the Perforce server encounters an error during
its processing of the request
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.editFiles(java.util.List, boolean, boolean, int, java.lang.String)
public List<IFileSpec> editFiles(List<IFileSpec> fileSpecs, EditFilesOptions opts) throws P4JavaException
IClient
editFiles
in interface IClient
fileSpecs
- non-null list of files to be opened, in Perforce client or
depot or local path format.opts
- possibly-null EditFilesOptions object specifying method options.
P4JavaException
- if an error occurs processing this method and its parametersIClient.editFiles(java.util.List, com.perforce.p4java.option.client.EditFilesOptions)
public List<IFileSpec> revertFiles(List<IFileSpec> fileSpecs, boolean noUpdate, int changeListId, boolean revertOnlyUnchanged, boolean noRefresh) throws ConnectionException, AccessException
IClient
revertFiles
in interface IClient
fileSpecs
- non-null (but possibly-empty) list of files to be revertednoUpdate
- if true, don't actually do the revert, just return the files that
would have been revertedchangeListId
- if positive, revert only those files in the pending changelist
given in changeListId.revertOnlyUnchanged
- if true, revert only those files which are opened
for edit or integrate and are unchanged or missing.noRefresh
- if true, bypass the client file refresh of the reverted files.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.revertFiles(java.util.List, boolean, int, boolean, boolean)
public List<IFileSpec> revertFiles(List<IFileSpec> fileSpecs, RevertFilesOptions opts) throws P4JavaException
IClient
revertFiles
in interface IClient
fileSpecs
- non-null (but possibly-empty) list of files to be revertedopts
- possibly-null RevertFilesOptions object specifying method options.
P4JavaException
- if an error occurs processing this method and its parametersIClient.revertFiles(java.util.List, com.perforce.p4java.option.client.RevertFilesOptions)
public List<IFileSpec> haveList(List<IFileSpec> fileSpecs) throws ConnectionException, AccessException
IClient
Note that this method will return an empty list unless the client is the IServer object's current client.
Only the depotFile, revision, clientPath, and localPath fields of the returned file specs are guaranteed to be valid.
haveList
in interface IClient
fileSpecs
- file specs; if empty or null, return all qualifying files
ConnectionException
- if the Perforce server is unreachable or is not
connected.t
AccessException
- if the Perforce server denies access to the callerIClient.haveList(java.util.List)
public List<IFileSpec> reopenFiles(List<IFileSpec> fileSpecs, int changeListId, String fileType) throws ConnectionException, AccessException
IClient
reopenFiles
in interface IClient
fileSpecs
- non-null list of files to be reopenedchangeListId
- the new changelist ID to be usedfileType
- if non-null, the file is reopened as that filetype.
If the filetype given is a partial filetype, that partial
filetype is combined with the current filetype.
See 'p4 help filetypes' to attempt to make any sense of this..
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.reopenFiles(java.util.List, int, java.lang.String)
public List<IFileSpec> reopenFiles(List<IFileSpec> fileSpecs, ReopenFilesOptions opts) throws P4JavaException
IClient
reopenFiles
in interface IClient
fileSpecs
- non-null list of files to be reopened.opts
- possibly-null ReopenFilesOptions object object specifying method options.
P4JavaException
- if an error occurs processing this method and its parameters.IClient.reopenFiles(java.util.List, com.perforce.p4java.option.client.ReopenFilesOptions)
public List<IFileSpec> where(List<IFileSpec> fileSpecs) throws ConnectionException, AccessException
IClient
Note that this method will return an empty list unless the client is the IServer object's current client.
The returned IFiles contain all three of the depot, client, and local file paths of the corresponding fileSpec array element where appropriate, or the usual server-generated error message if there was no corresponding mapping. The main exception to this is the case when no filespecs are given (i.e. the fileSpecs array is null or empty), when the mappings for '...' (all files in the current directory and below) are returned (if they exist).
where
in interface IClient
fileSpecs
- a list of Perforce file specifications; can be empty or even
null (see explanation above).
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.where(java.util.List)
public List<IFileSpec> openedFiles(List<IFileSpec> fileSpecs, int maxFiles, int changeListId) throws ConnectionException, AccessException
IClient
The returned list can be modified with the other arguments as described below.
openedFiles
in interface IClient
fileSpecs
- if non-empty, determine the status of the specified
files; otherwise return all qualifying files known to be openmaxFiles
- if positive, return only the first maxFiles qualifying files.changeListId
- if positive, return only files associated with the given
changelist ID.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.openedFiles(java.util.List, int, int)
public List<IFileSpec> openedFiles(List<IFileSpec> fileSpecs, OpenedFilesOptions opts) throws P4JavaException
IClient
Note that if a non-null OpenedFilesOptions object is passed to this method, the object's clientName field is ignored and the name of the client whose openedFiles method is being called is used instead; similarly, any allClient options (a.k.a "-a" flags) are also ignored.
openedFiles
in interface IClient
fileSpecs
- if non-empty, determine the status of the specified
files; otherwise return all qualifying files known to be openopts
- possibly-null OpenedFilesOptions object object specifying method options.
P4JavaException
- if an error occurs processing this method and its parameters.IClient.openedFiles(java.util.List, com.perforce.p4java.option.server.OpenedFilesOptions)
public List<IFileSpec> integrateFiles(int changeListId, boolean showActionsOnly, IntegrationOptions integOpts, String branchSpec, IFileSpec fromFile, IFileSpec toFile) throws ConnectionException, AccessException
IClient
integrateFiles
in interface IClient
changeListId
- if not IChangelist.UNKNOWN, use this as the target changelistshowActionsOnly
- if true, don't actually do the integration, just return
the actions that would have been doneintegOpts
- detailed integration objects. If null, the method will use default
option values as described for the IntegrationOptions constructor,
all of which are safe for straightforward merge use.branchSpec
- if not null, use this as the integration branch specification
(as in the -b option to integ).fromFile
- if not null, use this as the source Perforce filespectoFile
- if not null, use this as the target Perforce filespec
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.integrateFiles(int, boolean, com.perforce.p4java.core.file.IntegrationOptions, java.lang.String, com.perforce.p4java.core.file.IFileSpec, com.perforce.p4java.core.file.IFileSpec)
public List<IFileSpec> integrateFiles(IFileSpec fromFile, IFileSpec toFile, String branchSpec, IntegrateFilesOptions opts) throws P4JavaException
IClient
integrateFiles
in interface IClient
fromFile
- fromFile if not null, use this as the source Perforce filespectoFile
- toFile if not null, use this as the target Perforce filespecbranchSpec
- if not null, use this as the integration branch specification
(as in the -b option to integ)opts
- possibly-null IntegrateFilesOptions object specifying method options
P4JavaException
- if an error occurs processing this method and its parametersIClient.integrateFiles(com.perforce.p4java.core.file.IFileSpec, com.perforce.p4java.core.file.IFileSpec, java.lang.String, com.perforce.p4java.option.client.IntegrateFilesOptions)
public List<IFileSpec> integrateFiles(IFileSpec fromFile, List<IFileSpec> toFiles, IntegrateFilesOptions opts) throws P4JavaException
IClient
Note that depending on the specific options passed-in the fromFile can be null or one file spec; the toFiles list can be null, one or more file specs.
integrateFiles
in interface IClient
fromFile
- if not null, use this as the source file.toFiles
- if not null, use this as the list of target files.opts
- possibly-null IntegrateFilesOptions object specifying method options.
P4JavaException
- if an error occurs processing this method and its parameters.IClient.integrateFiles(com.perforce.p4java.core.file.IFileSpec, java.util.List, com.perforce.p4java.option.client.IntegrateFilesOptions)
public List<IFileSpec> resolveFilesAuto(List<IFileSpec> fileSpecs, boolean safeMerge, boolean acceptTheirs, boolean acceptYours, boolean showActionsOnly, boolean forceResolve) throws ConnectionException, AccessException
IClient
Note that this is currently a very limited version of the full Perforce resolve feature, corresponding only to (some of) the various auto-resolve features, meaning this method will never invoke (or need to invoke) end user interaction. More extensive versions of the resolve command will be surfaced as needed.
This method notionally returns an IFileSpec, as it's closely related to the integ method and shares many of its return values, but there are several limitations in the use of the returned IFileSpecs. In general, what is returned from this method is a mixture of resolution info messages (i.e. messages from the server that spell out what would or did happen during the resolve), and "true" filespecs. In the latter case, the filespec has a very limited set of valid fields: only client path, from file, and the from revisions are guaranteed to be valid. In the former case, since the info messages do NOT correspond one-to-one with the input file specs that caused the messages, consumers need to explicitly search each returned info message string for the relevant file path or name. This is an unfortunate artifact of the Perforce server's implementation of this command.
Note: results and behavior are undefined if clashing or inconsistent options are used with this method. In general, the behavior of (e.g.) setting both acceptYours and acceptTheirs true will be whatever the Perforce server makes of it (usually an error), but that's not guaranteed.... Note also that having safeMerge, acceptTheirs, acceptYours, and forceResolve all set to false results in "-am" behavior.
resolveFilesAuto
in interface IClient
fileSpecs
- files to be resolved; if null or empty, all files marked as
needing resolution will be processedsafeMerge
- if true, only do "safe" resolves, as documented for the p4 "-as" optionacceptTheirs
- if true, automatically accept "their" changes, as documented
for the p4 "-at" optionacceptYours
- if true, automatically accept "your" changes, as documented
for the p4 "-ay" optionshowActionsOnly
- if true, don't do the actual resolve, just return the
actions that would have been performed for the resolveforceResolve
- forces auto-mode resolve to accept the merged file even if
there are conflicts. This option results in a merged file that may
contain Perforce conflict markers; these markers should be edited out
of the file manually before it's submitted (unless you actually want
them there...).
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.resolveFilesAuto(java.util.List, boolean, boolean, boolean, boolean, boolean)
public List<IFileSpec> resolveFilesAuto(List<IFileSpec> fileSpecs, ResolveFilesAutoOptions opts) throws P4JavaException
IClient
Note that this is currently a very limited version of the full Perforce resolve feature, corresponding only to (some of) the various auto-resolve features, meaning this method will never invoke (or need to invoke) end user interaction. More extensive versions of the resolve command will be surfaced as needed.
This method notionally returns an IFileSpec, as it's closely related to the integ method and shares many of its return values, but there are several limitations in the use of the returned IFileSpecs. In general, what is returned from this method is a mixture of resolution info messages (i.e. messages from the server that spell out what would or did happen during the resolve), and "true" filespecs. In the latter case, the filespec has a very limited set of valid fields: only client path, from file, and the from revisions are guaranteed to be valid. In the former case, since the info messages do NOT correspond one-to-one with the input file specs that caused the messages, consumers need to explicitly search each returned info message string for the relevant file path or name. This is an unfortunate artifact of the Perforce server's implementation of this command.
Note: results and behavior are undefined if clashing or inconsistent options are used with this method. In general, the behavior of (e.g.) setting both acceptYours and acceptTheirs true will be whatever the Perforce server makes of it (usually an error), but that's not guaranteed.... Note also that having safeMerge, acceptTheirs, acceptYours, and forceResolve all set to false in the associated ResolveFilesAutoOptions object results in "-am" behavior.
resolveFilesAuto
in interface IClient
fileSpecs
- files to be resolved; if null or empty, all files marked as
needing resolution will be processedopts
- possibly-null ResolveFilesAutoOptions object specifying method option
P4JavaException
- if an error occurs processing this method and its parametersIClient.resolveFilesAuto(java.util.List, com.perforce.p4java.option.client.ResolveFilesAutoOptions)
public IFileSpec resolveFile(IFileSpec targetFile, InputStream sourceStream) throws ConnectionException, RequestException, AccessException
IClient
Note that this method assumes that the target and source resolve makes sense, and does little or no sanity- or error-checking. In particular, it will happily accept binary and text integration resolves whether they make sense or not; you should check the getHowResolved() method on the returned filespec to ensure that it did what you expected (typically this means checking that it was resolved using the "edit from" resolution rather than, say "ignored").
Use of this method will normally result in an integration edit record in the target file's history whether you've actually done an edit or not, so it is up to the consumer to weed out the various straight copy resolve cases and only use this for cases of more complex merges that actually did involve an edit (in reality or not).
Note that the IFileSpec returned will generally not have a valid depot or client file paths -- you must use the toFile and fromFile methods on the returns here.
resolveFile
in interface IClient
targetFile
- non-null file to be resolved.sourceStream
- non-null InputStream containing the resolved file's new contents.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerIClient.resolveFile(com.perforce.p4java.core.file.IFileSpec, java.io.InputStream)
public IFileSpec resolveFile(IFileSpec targetFile, InputStream sourceStream, boolean useTextualMerge, int startFromRev, int endFromRev) throws ConnectionException, RequestException, AccessException
IClient
Note that this method assumes that the target and source resolve makes sense, and does little or no sanity- or error-checking. In particular, it will happily accept binary and text integration resolves whether they make sense or not; you should check the getHowResolved() method on the returned filespec to ensure that it did what you expected (typically this means checking that it was resolved using the "edit from" resolution rather than, say "ignored").
Use of this method will normally result in an integration edit record in the target file's history whether you've actually done an edit or not, so it is up to the consumer to weed out the various straight copy resolve cases and only use this for cases of more complex merges that actually did involve an edit (in reality or not).
Note that the IFileSpec returned will generally not have a valid depot or client file paths -- you must use the toFile and fromFile methods on the returns here.
resolveFile
in interface IClient
targetFile
- non-null file to be resolved.sourceStream
- non-null InputStream containing the resolved file's new contents.useTextualMerge
- attempt a textual merge even for binary filesstartFromRev
- oldest revision to be resolved, or -1 for no limitendFromRev
- newest revision to be resolved, or -1 for no limit
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerIClient.resolveFile(com.perforce.p4java.core.file.IFileSpec, java.io.InputStream)
public List<IFileSpec> resolvedFiles(List<IFileSpec> fileSpecs, boolean showBaseRevision) throws ConnectionException, AccessException
IClient
resolvedFiles
in interface IClient
fileSpecs
- optional filespecs to be processedshowBaseRevision
- if true, reports the revision used as the base during
resolve (this seems to have no effect).
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.resolvedFiles(java.util.List, boolean)
public List<IFileSpec> resolvedFiles(List<IFileSpec> fileSpecs, ResolvedFilesOptions opts) throws P4JavaException
IClient
resolvedFiles
in interface IClient
fileSpecs
- fileSpecs optional filespecs to be processedopts
- possibly-null ResolveFilesAutoOptions object specifying method options
P4JavaException
- if an error occurs processing this method and its parametersIClient.resolvedFiles(java.util.List, com.perforce.p4java.option.client.ResolvedFilesOptions)
public List<IFileSpec> lockFiles(List<IFileSpec> fileSpecs, int changeListId) throws ConnectionException, AccessException
IClient
The open files named are locked in the Perforce depot, preventing any user other than the current user on the current client from submitting changes to the files. If a file is already locked then the lock request is rejected. If no file specs are given then lock all files currently open in the changelist number given if it is IChangelist.DEFAULT or > 0.
Note that the file specs returned are only partially filled out; the Perforce server seems to only return path information for this command.
lockFiles
in interface IClient
fileSpecs
- candidate file specschangeListId
- if IChangelist.DEFAULT or larger than zero, lock
all files associated this changelist ID
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.lockFiles(java.util.List, int)
public List<IFileSpec> lockFiles(List<IFileSpec> fileSpecs, LockFilesOptions opts) throws P4JavaException
IClient
The open files named are locked in the Perforce depot, preventing any user other than the current user on the current client from submitting changes to the files. If a file is already locked then the lock request is rejected. If no file specs are given then lock all files currently open in the changelist number given if it is IChangelist.DEFAULT or > 0.
Note that the file specs returned are only partially filled out; the Perforce server seems to only return path information for this command.
lockFiles
in interface IClient
fileSpecs
- candidate file specsopts
- possibly-null LockFilesOptions object specifying method options
P4JavaException
- if an error occurs processing this method and its parametersIClient.lockFiles(java.util.List, com.perforce.p4java.option.client.LockFilesOptions)
public List<IFileSpec> unlockFiles(List<IFileSpec> fileSpecs, int changeListId, boolean force) throws ConnectionException, AccessException
IClient
If the files are open in a specific pending changelist other than 'default', then the changeListId parameter is required to specify the pending changelist. If no file name is given then all files in the designated changelist are unlocked.
Note that the file specs returned are only partially filled out; the Perforce server seems to only return path information for this command.
unlockFiles
in interface IClient
fileSpecs
- candidate file specschangeListId
- if IChangelist.DEFAULT or larger than zero, lock
all files associated this changelist IDforce
- force the lock on non-owned filespecs. Requires appropriate
permissions.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
AccessException
- if the Perforce server denies access to the callerIClient.unlockFiles(java.util.List, int, boolean)
public List<IFileSpec> unlockFiles(List<IFileSpec> fileSpecs, UnlockFilesOptions opts) throws P4JavaException
IClient
Note that the file specs returned are only partially filled out; the Perforce server seems to only return path information for this command.
unlockFiles
in interface IClient
fileSpecs
- candidate file specsopts
- possibly-null UnlockFilesOptions object specifying method options
P4JavaException
- if an error occurs processing this method and its parametersIClient.unlockFiles(java.util.List, com.perforce.p4java.option.client.UnlockFilesOptions)
public List<IFileSpec> getDiffFiles(List<IFileSpec> fileSpecs, int maxFiles, boolean diffNonTextFiles, boolean openedDifferentMissing, boolean openedForIntegrate, boolean unopenedMissing, boolean unopenedDifferent, boolean unopenedWithStatus, boolean openedSame) throws ConnectionException, RequestException, AccessException
IClient
Note that this method returns lists of files, and is not useful to get the diffs themselves (at least not directly).
Note that the diff status returned for the unopenedWithStatus option is retrievable from the filespec with the getDiffStatus() method.
Note that you must have at least one of the various "-s" options set to true.
getDiffFiles
in interface IClient
fileSpecs
- candidate file specs; may be null.diffNonTextFiles
- include non-text files in the diff listsopenedDifferentMissing
- corresponds to the "-sa" option for the p4 command line.openedForIntegrate
- corresponds to the "-sb" option for the p4 command line.unopenedMissing
- corresponds to the "-sd" option for the p4 command line.unopenedDifferent
- corresponds to the "-se" option for the p4 command line.unopenedWithStatus
- corresponds to the "-sl" option for the p4 command line.openedSame
- corresponds to the "-sr" option for the p4 command line.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerIClient.getDiffFiles(java.util.List, int, boolean, boolean, boolean, boolean, boolean, boolean, boolean)
public List<IFileSpec> getDiffFiles(List<IFileSpec> fileSpecs, GetDiffFilesOptions opts) throws P4JavaException
IClient
Note that this method returns lists of files, and is not useful to get the diffs themselves (at least not directly).
Note that the diff status returned for the unopenedWithStatus option is retrievable from the filespec with the getDiffStatus() method.
Note that you must have at least one of the various "-s" options set to true.
getDiffFiles
in interface IClient
fileSpecs
- candidate file specs; may be null.opts
- possibly-null GetDiffFilesOptions object specifying method options
P4JavaException
- if an error occurs processing this method and its parametersIClient.getDiffFiles(java.util.List, com.perforce.p4java.option.client.GetDiffFilesOptions)
public List<IFileSpec> shelveFiles(List<IFileSpec> fileSpecs, int changelistId, ShelveFilesOptions opts) throws P4JavaException
IClient
shelveFiles
in interface IClient
fileSpecs
- list of files to be shelved; if null or empty, shelve all files
in the changelistchangelistId
- changelistId ID of the changelist containing the files to be shelved.
Can not be IChangelist.DEFAULT or IChangelist.UNKNOWN (both of
which will cause server usage errors to be returned if used).opts
- possibly-null ShelveFilesOptions object specifying method options
P4JavaException
- if an error occurs processing this method and its parametersIClient.shelveFiles(java.util.List, int, com.perforce.p4java.option.client.ShelveFilesOptions)
public List<IFileSpec> unshelveFiles(List<IFileSpec> fileSpecs, int sourceChangelistId, int targetChangelistId, UnshelveFilesOptions opts) throws P4JavaException
IClient
unshelveFiles
in interface IClient
fileSpecs
- list of files to be unshelved; if null or empty, shelve all files
in the changelistsourceChangelistId
- id of changelist containing shelved files to unshelvetargetChangelistId
- id of changelist unshelved files will be placed inopts
- possibly-null UnshelveFilesOptions object specifying method options
P4JavaException
- if an error occurs processing this method and its parametersIClient.unshelveFiles(java.util.List, int, int, com.perforce.p4java.option.client.UnshelveFilesOptions)
public List<IFileSpec> shelveChangelist(int changelistId, List<IFileSpec> fileSpecs, boolean forceUpdate, boolean replace, boolean discard) throws ConnectionException, RequestException, AccessException
IClient
shelveChangelist
in interface IClient
changelistId
- ID of the changelist containing the files to be shelved.
Can not be IChangelist.DEFAULT or IChangelist.UNKNOWN (both of
which will cause server usage errors to be returned if used).fileSpecs
- list of files to be shelved; if null or empty, shelve all files
in the changelistforceUpdate
- if true, update the named shelved files.replace
- if true, replace the named shelved files.discard
- if truem discard the named shelved files.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerIClient.shelveChangelist(int,
java.util.List, boolean, boolean, boolean)
public List<IFileSpec> shelveChangelist(IChangelist list) throws ConnectionException, RequestException, AccessException
IClient
This performs a 'p4 shelve -i' command when called.
shelveChangelist
in interface IClient
list
- non-null changelist to be shelved.
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerIClient.shelveChangelist(com.perforce.p4java.core.IChangelist)
public List<IFileSpec> unshelveChangelist(int shelveChangelistId, List<IFileSpec> fileSpecs, int clientChangelistId, boolean forceOverwrite, boolean previewOnly) throws ConnectionException, RequestException, AccessException
IClient
unshelveChangelist
in interface IClient
shelveChangelistId
- id of changelist containing shelved files to unshelve (-s)fileSpecs
- optional list of file specs to limit unshelving toclientChangelistId
- id of changelist to unshelve the files into (-c)forceOverwrite
- force clobbering of files currently writeable but unopened (-f)previewOnly
- don't actually unshelve but get the file specs that would be
unshelved (-n)
ConnectionException
- if the Perforce server is unreachable or is not
connected.
RequestException
- if the Perforce server encounters an error during
its processing of the request
AccessException
- if the Perforce server denies access to the callerIClient.unshelveChangelist(int,
java.util.List, int, boolean, boolean)
public List<IFileSpec> submitShelvedChangelist(int shelvedChangelistId) throws P4JavaException
IClient
This performs a 'p4 submit -e shelvedChange#' command when called.
submitShelvedChangelist
in interface IClient
shelvedChangelistId
- the shelved changelist to be submited.
P4JavaException
- if an error occurs processing this method and its parameters.IClient.submitShelvedChangelist(int)
public List<IFileSpec> copyFiles(IFileSpec fromFile, IFileSpec toFile, String branchSpec, CopyFilesOptions opts) throws P4JavaException
IClient
Corresponds to the 'p4 copy' command.
copyFiles
in interface IClient
fromFile
- if not null, use this as the source file.toFile
- if not null, use this as the target file.branchSpec
- if not null, use this as the copy branch specification.opts
- possibly-null CopyFilesOptions object specifying method options.
P4JavaException
- if an error occurs processing this method and its parameters.IClient.copyFiles(com.perforce.p4java.core.file.IFileSpec, com.perforce.p4java.core.file.IFileSpec, java.lang.String, com.perforce.p4java.option.client.CopyFilesOptions)
public List<IFileSpec> copyFiles(IFileSpec fromFile, List<IFileSpec> toFiles, CopyFilesOptions opts) throws P4JavaException
IClient
Note that depending on the specific options passed-in the fromFile can be null or one file spec; the toFiles list can be null, one or more file specs. The full semantics of this operation are found in the main 'p4 help copy' documentation.
copyFiles
in interface IClient
fromFile
- if not null, use this as the source file.toFiles
- if not null, use this as the list of target files.opts
- possibly-null CopyFilesOptions object specifying method options.
P4JavaException
- if an error occurs processing this method and its parameters.IClient.copyFiles(com.perforce.p4java.core.file.IFileSpec, java.util.List, com.perforce.p4java.option.client.CopyFilesOptions)
public List<IFileSpec> mergeFiles(IFileSpec fromFile, List<IFileSpec> toFiles, MergeFilesOptions opts) throws P4JavaException
IClient
Note that depending on the specific options passed-in the fromFile can be null or one file spec; the toFiles list can be null, one or more file specs.
mergeFiles
in interface IClient
fromFile
- if not null, use this as the source file.toFiles
- if not null, use this as the list of target files.opts
- possibly-null MergeFilesOptions object specifying method options
P4JavaException
- if an error occurs processing this method and its parametersIClient.mergeFiles(com.perforce.p4java.core.file.IFileSpec, java.util.List, com.perforce.p4java.option.client.MergeFilesOptions)
public List<IFileSpec> reconcileFiles(List<IFileSpec> fileSpecs, ReconcileFilesOptions opts) throws P4JavaException
IClient
'p4 reconcile' finds unopened files in a client's workspace and detects the following:
1. files in depot missing from workspace, but still on have list.
2. files on workspace that are not in depot.
3. files modified in workpace that are not opened for edit.
By default, the files matching each condition above in the path are reconciled by opening files for delete (scenario 1), add (scenario 2), and/or edit (scenario 3). The -e, -a, and -d flags may be used to limit to a subset of these operations. If no file arguments are given, reconcile and status default to the current working directory.
reconcileFiles
in interface IClient
fileSpecs
- non-null list of files to be opened, in Perforce client or
depot or local path format.opts
- possibly-null ReconcileFilesOptions object specifying method options.
P4JavaException
- if an error occurs processing this method and its parametersIClient.reconcileFiles(java.util.List, com.perforce.p4java.option.client.ReconcileFilesOptions)
public List<IFileSpec> populateFiles(IFileSpec fromFile, List<IFileSpec> toFiles, PopulateFilesOptions opts) throws P4JavaException
IClient
Note that depending on the specific options passed-in the fromFile can be null or one file spec; the toFiles list can be null, one or more file specs. The full semantics of this operation are found in the main 'p4 help populate' documentation.
populateFiles
in interface IClient
fromFile
- if not null, use this as the source file.toFiles
- if not null, use this as the list of target files.opts
- possibly-null PopulateFilesOptions object specifying method options.
P4JavaException
- if an error occurs processing this method and its parameters.IClient.populateFiles(com.perforce.p4java.core.file.IFileSpec, java.util.List, com.perforce.p4java.option.client.PopulateFilesOptions)
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |