maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Lamy (JIRA)" <>
Subject [jira] Updated: (SCM-562) Don't overwrite SVN auth cache
Date Wed, 07 Jul 2010 14:59:32 GMT


Olivier Lamy updated SCM-562:

    Fix Version/s: 1.4

> Don't overwrite SVN auth cache
> ------------------------------
>                 Key: SCM-562
>                 URL:
>             Project: Maven SCM
>          Issue Type: New Feature
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.3
>            Reporter: Carlos Sanchez
>             Fix For: 1.4
> From MRELEASE-497. Patch attached to that issue
> {quote}
> When release-plugin commit to SVN, it overwrites the auth cache with username/password
defined in the pom.xml.
> I want to use a separate username `maven' for maven-related commits, and personal username
`lenik' for personal development commits, when I start to using maven release plugin, it always
overwrite the auth cache with user `maven' , and I must do a "Tortoise/Settings/Saved Data/Clear
auth cache" before commit my personal changes.
> A recommend solution:
> add an option "--no-auth-cache" to svn commit command line will resolve this problem.
with option --no-auth-cache, the existing auth cache is left unchanged after commited.
> if there is an auth-cache option in pom.xml, say <auth-cache>false</auth-cache>
under <scm> element, it should be false be default.
> {quote}

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message