Java Doc for SVNRepository.java in  » Source-Control » tmatesoft-SVN » org » tmatesoft » svn » core » io » Java Source Code / Java DocumentationJava Source Code and Java Documentation

In particular this low-level protocol driver is used by the high-level API (represented by the org.tmatesoft.svn.core.wc package) when an access to a repository is needed.

It is important to say that before using the library it must be configured according to implimentations to be used. That is if a repository is assumed to be accessed either via the WebDAV protocol (http:// or https://), or a custom svn one (svn:// or svn+ssh://) or immediately on the local machine (file:///) a user must initialize the library in a proper way:

 //import neccessary classes
 import org.tmatesoft.svn.core.internal.io.fs.FSRepositoryFactory;
 import org.tmatesoft.svn.core.internal.io.dav.DAVRepositoryFactory;
 import org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryFactoryImpl;
 import org.tmatesoft.svn.core.SVNURL;
 import org.tmatesoft.svn.core.io.SVNRepository;
 import org.tmatesoft.svn.core.io.SVNRepositoryFactory;
 import import org.tmatesoft.svn.core.wc.SVNWCUtil;
 import import org.tmatesoft.svn.core.SVNException;
 ...
 //Set up connection protocols support:
 //http:// and https://
 DAVRepositoryFactory.setup();
 //svn://, svn+xxx:// (svn+ssh:// in particular)
 SVNRepositoryFactoryImpl.setup();
 //file:///
 FSRepositoryFactory.setup();
 

So, only after these setup steps the client can create http | svn | file protocol implementations of the SVNRepository abstract class to access the repository.

This is a general way how a user creates an SVNRepository driver object:

 String url="http://svn.collab.net/svn/trunk";
 String name="my name";
 String password="my password";
 repository = null;
 try { 
 repository = SVNRepositoryFactory.create(SVNURL.parseURIDecoded(url));
 ISVNAuthenticationManager authManager = 
 SVNWCUtil.createDefaultAuthenticationManager(name, password);
 repository.setAuthenticationManager(authManager);
 ...
 } catch (SVNException e){
 e.printStackTrace();
 System.exit(1);
 }
 //work with the repository
 ... 

SVNRepository objects are not thread-safe, we're strongly recommend you not to use one SVNRepository object from within multiple threads.

Also methods of SVNRepository objects are not reenterable - that is, you can not call operation methods of an SVNRepository driver neither from within those handlers that are passed to some of the driver's methods, nor during committing with the help of a commit editor (until the editor's ISVNEditor.closeEdit closeEdit() method is called).

To authenticate a user over network SVNRepository drivers use ISVNAuthenticationManager auth drivers.
version:
   1.1.1
author:
   TMate Software Ltd.
See Also:   SVNRepositoryFactory
See Also:   org.tmatesoft.svn.core.auth.ISVNAuthenticationManager
See Also:    Examples

target is the name (one-level path component) of an entry that will restrict the scope of the checkout to this entry.

If contents arg is not null it will be written with file contents.

If properties arg is not null it will receive the properties of the file.

Note that locking is never anonymous, so any server implementing this function will have to "pull" a username from the client, if it hasn't done so already.

Each path to be locked is handled with the provided handler. If a path was successfully locked, the handler's ISVNLockHandler.handleLock(StringSVNLockSVNErrorMessage) handleLock() is called that receives the path and either a lock object (representing the lock that was set on the path) or an error exception, if locking failed for that path.

If any path is already locked by a different user and the force flag is false, then this call fails with throwing an SVNException.

Changes will be limited to those that occur under a session's URL, and the server will assume that the client has no knowledge of revisions prior to a lowRevision.

target is the name (one-level path component) of an entry that will restrict the scope of the status to this entry.

target is the name (one-level path component) of an entry that will restrict the scope of the update to this entry.

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").
Parameters:
  path - an item's path
Parameters:
  revision - a revision number the node kind for the given path at the given revision
throws:
  SVNException - if a failure occured while connecting to a repository or the user's authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

target is the name (one-level path component) of an entry that will restrict the scope of the checkout to this entry. In other words target is a child entry of the directory represented by the repository location to which this object is set. For example, if we have something like "/dirA/dirB" in a repository, then this object's repository location may be set to "svn://host:port/path/to/repos/dirA", and target may be "dirB".

If target is null or empty ("") then the scope of the checkout operation is the repository location to which this object is set.

The provided editor is used to carry out all the work on building a local tree of dirs and files being checked out.

NOTE: you may not invoke methods of this SVNRepository object from within the provided editor.
Parameters:
  revision - a desired revision of a dir to check out; defaultsto the latest revision (HEAD)
Parameters:
  target - an entry name (optional)
Parameters:
  recursive - if true and the checkout scope is a directory, descends recursively, otherwise not
Parameters:
  editor - a caller's checkout editor
throws:
  SVNException - in the following cases:

• the checkout scope is not a directory (only dirs canbe checked out)
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

target is the name (one-level path component) of an entry that will restrict the scope of the diff operation to this entry. In other words target is a child entry of the directory represented by the repository location to which this object is set. For example, if we have something like "/dirA/dirB" in a repository, then this object's repository location may be set to "svn://host:port/path/to/repos/dirA", and target may be "dirB".

If target is null or empty ("") then the scope of the diff operation is the repository location to which this object is set.

The reporter is used to describe the state of the target item(s) (i.e. items' revision numbers). All the paths described by the reporter should be relative to the repository location to which this object is set.

After that the editor is used to carry out all the work on evaluating differences against url. This editor contains knowledge of where the change will begin (when ISVNEditor.openRoot(long) ISVNEditor.openRoot() is called).

If ignoreAncestry is false then the ancestry of the paths being diffed is taken into consideration - they are treated as related. In this case, for example, if calculating differences between two files with identical contents but different ancestry, the entire contents of the target file is considered as having been removed and added again.

If ignoreAncestry is true then the two paths are merely compared ignoring the ancestry.

NOTE: you may not invoke methods of this SVNRepository object from within the provided reporter and editor.
Parameters:
  url - a repository location of the entry against which differences are calculated
Parameters:
  targetRevision - a revision number of the entry located at the specified url; defaults to thelatest revision (HEAD) if this arg is invalid
Parameters:
  revision - a revision number of the repository location to which this driver object is set
Parameters:
  target - a target entry name (optional)
Parameters:
  ignoreAncestry - if true thenthe ancestry of the two entries to be diffed is ignored, otherwise not
Parameters:
  recursive - if true and the diff scopeis a directory, descends recursively, otherwise not
Parameters:
  getContents - if false contents (diff windows) will not be sent ot the editor.
Parameters:
  reporter - a caller's reporter
Parameters:
  editor - a caller's editor
throws:
  SVNException - in the following cases:

• url not found neither in the specified revision nor in the HEAD revision
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

target is the name (one-level path component) of an entry that will restrict the scope of the diff operation to this entry. In other words target is a child entry of the directory represented by the repository location to which this object is set. For example, if we have something like "/dirA/dirB" in a repository, then this object's repository location may be set to "svn://host:port/path/to/repos/dirA", and target may be "dirB".

If target is null or empty ("") then the scope of the diff operation is the repository location to which this object is set.

The reporter is used to describe the state of the target item(s) (i.e. items' revision numbers). All the paths described by the reporter should be relative to the repository location to which this object is set.

After that the editor is used to carry out all the work on evaluating differences against url. This editor contains knowledge of where the change will begin (when ISVNEditor.openRoot(long) ISVNEditor.openRoot() is called).

If ignoreAncestry is false then the ancestry of the paths being diffed is taken into consideration - they are treated as related. In this case, for example, if calculating differences between two files with identical contents but different ancestry, the entire contents of the target file is considered as having been removed and added again.

If ignoreAncestry is true then the two paths are merely compared ignoring the ancestry.

NOTE: you may not invoke methods of this SVNRepository object from within the provided reporter and editor.
Parameters:
  url - a repository location of the entry against which differences are calculated
Parameters:
  revision - a revision number of the repository location to which this driver object is set
Parameters:
  target - a target entry name (optional)
Parameters:
  ignoreAncestry - if true thenthe ancestry of the two entries to be diffed is ignored, otherwise not
Parameters:
  recursive - if true and the diff scopeis a directory, descends recursively, otherwise not
Parameters:
  reporter - a caller's reporter
Parameters:
  editor - a caller's editor
throws:
  SVNException - in the following cases:

• url not found neither in the specified revision nor in the HEAD revision
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

mediator is used for temporary delta data storage allocations.

The root path of the commit is the current repository location to which this object is set.

After the commit has succeeded ISVNEditor.closeEdit ISVNEditor.closeEdit() returns an SVNCommitInfo object that contains a new revision number, the commit date, commit author.

This method should be rather used with pre-1.2 repositories.

NOTE: you may not invoke methods of this SVNRepository object from within the returned commit editor.
Parameters:
  logMessage - a commit log message
Parameters:
  mediator - temp delta storage provider; used also to cachewcprops while committing an editor to commit a local tree of dirs and/or files
throws:
  SVNException - in the following cases:

• the repository location this object is set to is not a directory
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

locks is a map used to provide lock tokens on the locked paths. Keys are locked paths in a local tree, and each value for a key is a lock token. locks must live during the whole commit operation.

If keepLocks is true, then the locked paths won't be unlocked after a successful commit. Otherwise, if false, locks will be automatically released.

mediator is used for temporary delta data storage allocations.

The root path of the commit is the current repository location to which this object is set.

After the commit has succeeded ISVNEditor.closeEdit ISVNEditor.closeEdit() returns an SVNCommitInfo object that contains a new revision number, the commit date, commit author.

NOTE: you may not invoke methods of this SVNRepository object from within the returned commit editor.
Parameters:
  logMessage - a commit log message
Parameters:
  locks - a map containing locked paths mapped to lock tokens
Parameters:
  keepLocks - true to keep existing locks; false to release locks after the commit
Parameters:
  mediator - temp delta storage provider; used also to cachewcprops while committing an editor to commit a local tree of dirs and/or files
throws:
  SVNException - in the following cases:

• the repository location this object is set to is not a directory
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

Example: if you specify a single date without specifying a time of the day (e.g. 2002-11-27) the timestamp is assumed to 00:00:00 and the method won't return any revisions for the day you have specified but for the day just before it.
Parameters:
  date - a datestamp for defining the neededmoment in time the revision of the repositoryfor that time
throws:
  SVNException - if a failure occured while connecting to a repository or the user's authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

If no debug logger has been specified by the time this call occurs, a default one (returned by org.tmatesoft.svn.util.SVNDebugLog.getDefaultLog()) will be created and used. a debug logger

If handler arg is not null it will be dispatched information of each directory entry represented by an SVNDirEntry object.

If properties arg is not null it will receive the properties of the file. This includes all properties: not just ones controlled by a user and stored in the repository filesystem, but also non-tweakable ones (e.g. 'wcprops', 'entryprops', etc.). Property names (keys) are mapped to property values.

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").

If revision is invalid (negative), HEAD revision will be used. NOTE: you may not invoke operation methods of this SVNRepository object from within the provided handler.
Parameters:
  path - a directory path
Parameters:
  revision - a directory revision
Parameters:
  properties - a directory properties receiver map
Parameters:
  handler - a handler to process directory entries the revision of the directory
throws:
  SVNException - in the following cases:

• path not found in the specified revision
• path is not a directory
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").
Parameters:
  path - a directory path
Parameters:
  revision - a revision number
Parameters:
  properties - if not null then alldirectory properties (including non-tweakable ones)will be put into this map (where keys are property namesand mappings are property values)
Parameters:
  dirEntries - if not null then thiscollection receives fetched dir entries (SVNDirEntry objects) a collection containing fetched directory entries (SVNDirEntry objects)
throws:
  SVNException - in the following cases:

• path not found in the specified revision
• path is not a directory
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

If entries arg is not null it receives the directory entries. Information of each directory entry is represented by an SVNDirEntry object.

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").
Parameters:
  path - a directory path
Parameters:
  revision - a revision number
Parameters:
  includeCommitMessages - if true thendir entries (SVNDirEntry objects) will be supplied with commit log messages, otherwise not
Parameters:
  entries - a collection that receives fetched dir entries the directory entry itself which contentsare fetched into entries
throws:
  SVNException - in the following cases:

• path not found in the specified revision
• path is not a directory
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

If contents arg is not null it will be written with file contents.

If properties arg is not null it will receive the properties of the file. This includes all properties: not just ones controlled by a user and stored in the repository filesystem, but also non-tweakable ones (e.g. 'wcprops', 'entryprops', etc.). Property names (keys) are mapped to property values.

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").

If revision is invalid (negative), HEAD revision will be used.
Parameters:
  path - a file path
Parameters:
  revision - a file revision
Parameters:
  properties - a file properties receiver map
Parameters:
  contents - an output stream to write the file contents to the revision the file has been taken at
throws:
  SVNException - in the following cases:

• there's no such path in revision
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

A file revision is represented by an SVNFileRevision object. Each file revision is handled by the file revision handler provided. Only those revisions will be retrieved in which the file was changed. The iteration will begin at the first such revision starting from the startRevision and so on - up to the endRevision. If the method succeeds, the provided handler will have been invoked at least once.

For the first interesting revision the file contents will be provided to the handler as a text delta against an empty file. For the following revisions, the delta will be against the fulltext contents of the previous revision.

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").

NOTES:

• you may not invoke methods of this SVNRepository object from within the provided handler
• this functionality is not available in pre-1.1 servers

A file revision is represented by an SVNFileRevision object. Only those revisions will be retrieved in which the file was changed. The iteration will begin at the first such revision starting from the startRevision and so on - up to the endRevision.

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").

NOTE: this functionality is not available in pre-1.1 servers
Parameters:
  path - a file path
Parameters:
  revisions - if not null this collectionwill receive all the fetched file revisions
Parameters:
  sRevision - a revision to start from
Parameters:
  eRevision - a revision to stop at a collection that keeps file revisions - SVNFileRevision instances
throws:
  SVNException - if a failure occured while connecting to a repository or the user's authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)
See Also:   SVNRepository.getFileRevisions(String,long,long,ISVNFileRevisionHandler)
See Also:   SVNFileRevision
since:
   SVN 1.1

For each interesting revision (taken from revisions) an entry location is represented by an SVNLocationEntry object which is passed to the provided handler. Each SVNLocationEntry object represents a repository path in a definite revision.

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").

NOTES:

• you may not invoke methods of this SVNRepository object from within the provided handler
• this functionality is not available in pre-1.1 servers

• path not found in the specified pegRevision
• pegRevision is not valid
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

For each interesting revision (taken from revisions) an entry location is represented by an SVNLocationEntry object. Each SVNLocationEntry object represents a repository path in a definite revision.

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").

NOTE: this functionality is not available in pre-1.1 servers
Parameters:
  path - an item's path
Parameters:
  entries - if not null then this collection object receives entry locations
Parameters:
  pegRevision - a revision in which path is first looked up
Parameters:
  revisions - an array of numbers of interesting revisions in whichlocations are looked up. If path doesn't exist in an interesting revision, that revision will be ignored. a collection with retrieved entry locations
throws:
  SVNException - in the following cases:

• path not found in the specified pegRevision
• pegRevision is not valid
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

For each interesting revision (taken from revisions) an entry location is represented by an SVNLocationEntry object. Each SVNLocationEntry object represents a repository path in a definite revision.

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").

NOTE: this functionality is not available in pre-1.1 servers
Parameters:
  path - an item's path
Parameters:
  entries - if not null then this map object receives entry locations (which keys are revisionnumbers as Longs and mappings are entry locations objects)
Parameters:
  pegRevision - a revision in which path is first looked up
Parameters:
  revisions - an array of numbers of interesting revisions in whichlocations are looked up. If path doesn't exist in an interesting revision, that revision will be ignored. a map (which keys are revision numbers as Longs and mappings are entry locations objects) with collected entry locations
throws:
  SVNException - in the following cases:

• path not found in the specified pegRevision
• pegRevision is not valid
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").
Parameters:
  path - a file path an SVNLock instance (representing the lock) or null if there's no lock
throws:
  SVNException - in the following cases:

• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").
Parameters:
  path - a path under which locks are to be retrieved an array of SVNLock objects (representing locks)
throws:
  SVNException - in the following cases:

• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

• revision number is invalid
• there's no such revision at all
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

• revision number is invalid orif there's no such revision at all.
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

The path arg can be both relative to the location of this driver and absolute to the repository root (starts with "/").
Parameters:
  path - an item's path
Parameters:
  revision - a revision of the entry; defaults to the latest revision (HEAD) an SVNDirEntry containing information aboutthe entry or null if there's no entry with at the specified path under the specified revision
throws:
  SVNException - in the following cases:

• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

Note that locking is never anonymous, so any server implementing this function will have to "pull" a username from the client, if it hasn't done so already.

Each path to be locked is handled with the provided handler. If a path was successfully locked, the handler's ISVNLockHandler.handleLock(StringSVNLockSVNErrorMessage) handleLock() is called that receives the path and either a lock object (representing the lock that was set on the path) or an error exception, if locking failed for that path.

If any path is already locked by a different user and the force flag is false, then this call fails with throwing an SVNException. But if force is true, then the existing lock(s) will be "stolen" anyway, even if the user name does not match the current lock's owner.

Paths can be both relative to the location of this driver and absolute to the repository root (starting with "/").
Parameters:
  pathsToRevisions - a map which keys are paths and values are revision numbers (as Longs); paths are strings and revision numbers are Long objects
Parameters:
  comment - a comment string for the lock (optional)
Parameters:
  force - true if the file is to be locked in any way (even if it's already locked by someone else)
Parameters:
  handler - if not null, the lockhandler is invoked on each path to be locked
throws:
  SVNException - in the following cases:

• force is falseand a path is already locked by someone else
• a revision of a path is less than its last changed revision
• a path does not exist in the latest revision
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

This method invokes handler on each log entry from startRevision to endRevision. startRevision may be greater or less than endRevision; this just controls whether the log messages are processed in descending or ascending revision number order.

If startRevision or endRevision is invalid, it defaults to the youngest.

If targetPaths has one or more elements, then only those revisions are processed in which at least one of targetPaths was changed (i.e., if a file text or properties changed; if dir properties changed or an entry was added or deleted). Each path is relative to the repository location that this object is set to.

If changedPath is true, then each SVNLogEntry passed to the handler will contain info about all paths changed in that revision it represents. To get them call org.tmatesoft.svn.core.SVNLogEntry.getChangedPaths that returns a map, which keys are the changed paths and the values are SVNLogEntryPath objects. If changedPath is false, changed paths info will not be provided.

If strictNode is true, copy history will not be traversed (if any exists) when harvesting the revision logs for each path.

Target paths can be both relative to the location of this driver and absolute to the repository root (starts with "/").

NOTE: you may not invoke methods of this SVNRepository object from within the provided handler.
Parameters:
  targetPaths - paths that mean only those revisions at which they were changed
Parameters:
  startRevision - a revision to start from
Parameters:
  endRevision - a revision to end at
Parameters:
  changedPath - if true thenrevision information will also include all changed paths per revision, otherwise not
Parameters:
  strictNode - if true then copy history (if any) is not to be traversed
Parameters:
  handler - a caller's handler that will be dispatched log entry objects the number of revisions traversed
throws:
  SVNException - if a failure occured while connecting to a repository or the user's authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)
See Also:   SVNRepository.log(String[],Collection,long,long,boolean,boolean)
See Also:   SVNRepository.log(String[],long,long,boolean,boolean,long,ISVNLogEntryHandler)
See Also:   org.tmatesoft.svn.core.ISVNLogEntryHandler
See Also:   org.tmatesoft.svn.core.SVNLogEntry
See Also:   org.tmatesoft.svn.core.SVNLogEntryPath

This method invokes handler on each log entry from startRevision to endRevision. startRevision may be greater or less than endRevision; this just controls whether the log messages are processed in descending or ascending revision number order.

If startRevision or endRevision is invalid, it defaults to the youngest.

If targetPaths has one or more elements, then only those revisions are processed in which at least one of targetPaths was changed (i.e., if a file text or properties changed; if dir properties changed or an entry was added or deleted). Each path is relative to the repository location that this object is set to.

If changedPath is true, then each SVNLogEntry passed to the handler will contain info about all paths changed in that revision it represents. To get them call org.tmatesoft.svn.core.SVNLogEntry.getChangedPaths that returns a map, which keys are the changed paths and the values are SVNLogEntryPath objects. If changedPath is false, changed paths info will not be provided.

If strictNode is true, copy history will not be traversed (if any exists) when harvesting the revision logs for each path.

If limit is > 0 then only the first limit log entries will be handled. Otherwise (i.e. if limit is 0) this number is ignored.

Target paths can be both relative to the location of this driver and absolute to the repository root (starts with "/").

NOTE: you may not invoke methods of this SVNRepository object from within the provided handler.
Parameters:
  targetPaths - paths that mean only those revisions at which they were changed
Parameters:
  startRevision - a revision to start from
Parameters:
  endRevision - a revision to end at
Parameters:
  changedPath - if true thenrevision information will also include all changed paths per revision, otherwise not
Parameters:
  strictNode - if true then copy history (if any) is not to be traversed
Parameters:
  limit - the maximum number of log entries to process
Parameters:
  handler - a caller's handler that will be dispatched log entry objects the number of revisions traversed
throws:
  SVNException - if a failure occured while connecting to a repository or the user's authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)
See Also:   SVNRepository.log(String[],Collection,long,long,boolean,boolean)
See Also:   SVNRepository.log(String[],long,long,boolean,boolean,long,ISVNLogEntryHandler)
See Also:   org.tmatesoft.svn.core.ISVNLogEntryHandler
See Also:   org.tmatesoft.svn.core.SVNLogEntry
See Also:   org.tmatesoft.svn.core.SVNLogEntryPath

startRevision may be greater or less than endRevision; this just controls whether the log messages are processed in descending or ascending revision number order.

If startRevision or endRevision is invalid, it defaults to the youngest.

If targetPaths has one or more elements, then only those revisions are processed in which at least one of targetPaths was changed (i.e., if a file text or properties changed; if dir properties changed or an entry was added or deleted). Each path is relative to the repository location that this object is set to.

If changedPath is true, then each SVNLogEntry object is supplied with info about all paths changed in that revision it represents. To get them call org.tmatesoft.svn.core.SVNLogEntry.getChangedPaths that returns a map, which keys are the changed paths and the mappings are SVNLogEntryPath objects. If changedPath is false, changed paths info will not be provided.

If strictNode is true, copy history will not be traversed (if any exists) when harvesting the revision logs for each path.

Target paths can be both relative to the location of this driver and absolute to the repository root (starts with "/").
Parameters:
  targetPaths - paths that mean only those revisions at which they were changed
Parameters:
  entries - if not null then this collectionwill receive log entries
Parameters:
  startRevision - a revision to start from
Parameters:
  endRevision - a revision to end at
Parameters:
  changedPath - if true thenrevision information will also include all changed paths per revision, otherwise not
Parameters:
  strictNode - if true then copy history (if any) is not to be traversed a collection with log entries
throws:
  SVNException - if a failure occured while connecting to a repository or the user's authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)
See Also:   SVNRepository.log(String[],long,long,boolean,boolean,ISVNLogEntryHandler)
See Also:   SVNRepository.log(String[],long,long,boolean,boolean,long,ISVNLogEntryHandler)
See Also:   org.tmatesoft.svn.core.ISVNLogEntryHandler
See Also:   org.tmatesoft.svn.core.SVNLogEntry
See Also:   org.tmatesoft.svn.core.SVNLogEntryPath

Changes will be limited to those that occur under a session's URL, and the server will assume that the client has no knowledge of revisions prior to a lowRevision. These two limiting factors define the portion of the tree that the server will assume the client already has knowledge of, and thus any copies of data from outside that part of the tree will be sent in their entirety, not as simple copies or deltas against a previous version.

If sendDeltas is null, the actual text and property changes in the revision will be sent, otherwise no text deltas and null property changes will be sent instead.

If lowRevision is invalid, it defaults to 0.
Parameters:
  lowRevision - a low revision point beyond which a client has noknowledge of paths history
Parameters:
  revision - a revision to replay
Parameters:
  sendDeltas - controls whether text and property changes are to besent
Parameters:
  editor - a commit editor to receive changes
throws:
  SVNException -
since:
   1.1, new in SVN 1.4

But you can not specify a new repository location url with a protocol different from the one used for the previous (essentially, the current) repository location, since SVNRepository objects are protocol dependent.

If a new url is located within the same repository, this object just switches to that url not closing the current session (i.e. not calling SVNRepository.closeSession() ).

If either a new url refers to the same host (including a port number), or refers to an absolutely different host, or this object has got no repository root location cached (hasn't ever accessed a repository yet), or forceReconnect is true, then the current session is closed, cached repository credentials (UUID and repository root directory location ) are reset and this object is switched to a new repository location.
Parameters:
  url - a new repository location url
Parameters:
  forceReconnect - if true thenforces to close the current session, resets thecached repository credentials and switches this object to a new location (doesn't matter whether it's on the same host or not)
throws:
  SVNException - if the old url and a new one has got differentprotocols

NOTE: revision properties are not versioned. So, the old values may be lost forever.
Parameters:
  revision - the number of the revision which property is tobe changed
Parameters:
  propertyName - a revision property name
Parameters:
  propertyValue - the value of the revision property
throws:
  SVNException - in the following cases:

• the repository is configured not to allow clientsto modify revision properties (e.g. a pre-revprop-change-hookprogram is not found or failed)
• revision is invalid or doesn't exist at all
• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

If one would like to have a standard Subversion behaviour (when tunnel commands are fetched from the config file beneath the section named tunnels), he should provide a default provider (default implementation of the org.tmatesoft.svn.core.wc.ISVNOptions interface). Refer to org.tmatesoft.svn.core.wc.SVNWCUtil class for more details on how to get a default options driver.
Parameters:
  tunnelProvider - a tunnel provider
See Also:   SVNRepository.getTunnelProvider()

target is the name (one-level path component) of an entry that will restrict the scope of the status to this entry. In other words target is a child entry of the directory represented by the repository location to which this object is set. For example, if we have something like "/dirA/dirB" in a repository, then this object's repository location may be set to "svn://host:port/path/to/repos/dirA", and target may be "dirB".

If target is null or empty ("") then the scope of the update operation is the repository location to which this object is set.

The reporter is used to describe the state of the local item(s) (i.e. items' revision numbers, deleted, switched items). All the paths described by the reporter should be relative to the repository location to which this object is set.

After that the editor is used to carry out all the work on performing status. This editor contains knowledge of where the change will begin (when ISVNEditor.openRoot(long) ISVNEditor.openRoot() is called).

NOTE: you may not invoke methods of this SVNRepository object from within the provided reporter and editor.
Parameters:
  revision - a desired revision to get status against; defaults tothe latest revision (HEAD)
Parameters:
  target - an entry name (optional)
Parameters:
  recursive - if true and the status scopeis a directory, descends recursively, otherwise not
Parameters:
  reporter - a client's reporter-baton
Parameters:
  editor - a client's status editor
throws:
  SVNException - in the following cases:

• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

Note that unlocking is never anonymous, so any server implementing this function will have to "pull" a username from the client, if it hasn't done so already.

Each path to be unlocked is handled with the provided handler. If a path was successfully unlocked, the handler's ISVNLockHandler.handleUnlock(StringSVNLockSVNErrorMessage) handleUnlock() is called that receives the path and either a lock object (representing the lock that was removed from the path) or an error exception, if unlocking failed for that path.

If the username doesn't match the lock's owner and force is false, this method call fails with throwing an SVNException. But if the force flag is true, the lock will be "broken" by the current user.

Also if the lock token is incorrect or null and force is false, the method fails with throwing a SVNException. However, if force is true the lock will be removed anyway.

Paths can be both relative to the location of this driver and absolute to the repository root (starting with "/").
Parameters:
  pathToTokens - a map which keys are file paths and values are file locktokens (both keys and values are strings)
Parameters:
  force - true to remove the lock in any case - i.e. to "break" the lock
Parameters:
  handler - if not null, the lockhandler is invoked on each path to be unlocked
throws:
  SVNException - in the following cases:

• force is falseand the name of the user who tries to unlock a path does not matchthe lock owner
• a lock token is incorrect for a path
• a failure occurred while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

target is the name (one-level path component) of an entry that will restrict the scope of the update to this entry. In other words target is a child entry of the directory represented by the repository location to which this object is set. For example, if we have something like "/dirA/dirB" in a repository, then this object's repository location may be set to "svn://host:port/path/to/repos/dirA", and target may be "dirB".

If target is null or empty ("") then the scope of the update operation is the repository location to which this object is set.

The reporter is used to describe the state of the local item(s) (i.e. items' revision numbers, deleted, switched items). All the paths described by the reporter should be relative to the repository location to which this object is set.

After that the editor is used to carry out all the work on updating. This editor contains knowledge of where the change will begin (when ISVNEditor.openRoot(long) ISVNEditor.openRoot() is called).

NOTE: you may not invoke methods of this SVNRepository object from within the provided reporter and editor.
Parameters:
  revision - a desired revision to make update to; defaults tothe latest revision (HEAD)
Parameters:
  target - an entry name (optional)
Parameters:
  recursive - if true and the update scopeis a directory, descends recursively, otherwise not
Parameters:
  reporter - a caller's reporter
Parameters:
  editor - a caller's editor
throws:
  SVNException - in the following cases:

• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)

Updates a path as it's described for the SVNRepository.update(long,String,boolean,ISVNReporterBaton,ISVNEditor) update() method using the provided reporter and editor, and switching it to a new repository location.

NOTE: you may not invoke methods of this SVNRepository object from within the provided reporter and editor.
Parameters:
  url - a new location in the repository to switch to
Parameters:
  revision - a desired revision to make update to; defaultsto the latest revision (HEAD)
Parameters:
  target - an entry name (optional)
Parameters:
  recursive - if true and the switch scopeis a directory, descends recursively, otherwise not
Parameters:
  reporter - a caller's reporter
Parameters:
  editor - a caller's editor
throws:
  SVNException - in the following cases:

• a failure occured while connecting to a repository
• the user authentication failed (see org.tmatesoft.svn.core.SVNAuthenticationException)