[ http://jira.codehaus.org/browse/MRELEASE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed MRELEASE-497. --------------------------------- Resolution: Fixed fixed with SCM-562 > Don't overwrite SVN auth cache > ------------------------------ > > Key: MRELEASE-497 > URL: http://jira.codehaus.org/browse/MRELEASE-497 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: perform, prepare, scm > Environment: Windows XP, JDK 1.7, SVN 1.6.5 > Reporter: Lenik > Assignee: Olivier Lamy > Priority: Critical > Fix For: 2.1 > > Attachments: no-auth-cache.patch > > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira