Skip to main content

svn credentials caching

Image
By
SVN client has a built-in system for caching authentication credentials on disk. It saves the credentials in the user's private runtime configuration area

~/.subversion/auth/ (Unix-like systems)
%APPDATA%/Subversion/auth/ (Windows)


If you dont want to catch the credeitials for a commit, use --no-auth-cache.
$ svn commit --no-auth-cache

Here we are telling the svn client that dont cach authentication credentials.

You can disable credential caching permanently by editing your runtime config file (located next to the auth/ directory). Set store-auth-creds to no.

[auth]
store-auth-creds = no
Labels:

Comments

Post a Comment

Popular posts from this blog

SVN red book

By
I normally use Subclipse plugin for Eclipse for SVN operations. It really makes life easy. I am a novice when it comes to performing svn operations using SVN commands. I found a very useful resource for that: HTML version of SVN red book (for subversion 1.5) Hope you find this useful :)
Post a Comment
Read more

How to upload an artifact to maven remote repository?

By
If you want to deploy artifacts that were not build using maven, or which were build using maven but their POMs did not contains the deployment detials, then you need to deploy them using the following: mvn -e deploy:deploy-file -DgroupId=com.test.jpa -DartifactId=jpa-demo -Dversion=1.0.0 -Dpackaging=jar -Dfile=jpa-demo-1.0.0.jar -Durl=http://localhost:8080/archiva/repository/internal/ -DrepositoryId=reppoI d url: specifies the remote maven repository to where the jar is to be uploaded repositoryId: Id repository is secured, repositoryId is used to specify the credentials that are to be used for uploading. Repositories are defined in settings.xml. e.g. <servers>     <server>       <id>deploymentRepo</id>       <username>repouser</username>       <password>repopwd</password>     </server> </servers> Mave...
Post a Comment
Read more