[
https://issues.apache.org/jira/browse/SCM-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964722#comment-17964722
]
Olivier Lamy commented on SCM-562:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#772|https://github.com/apache/maven-scm/issues/772].
> Don't overwrite SVN auth cache
> ------------------------------
>
> Key: SCM-562
> URL: https://issues.apache.org/jira/browse/SCM-562
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-scm-provider-svn
> Affects Versions: 1.3
> Reporter: Carlos Sanchez Gonzalez
> Assignee: Olivier Lamy
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
