maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lenik (JIRA)" <>
Subject [jira] Issue Comment Edited: (MRELEASE-497) Don't overwrite SVN auth cache
Date Wed, 11 Nov 2009 07:06:56 GMT


Lenik edited comment on MRELEASE-497 at 11/11/09 1:06 AM:


      was (Author: lenik):
    I hate JIRA, all the operation buttons is on the left bar, when I want to add a comment,
I just can't find where I shall click at! Why can't put a comment button just below this form?

I posted this issue last month, now tens of days passed, there is no one mentioned at all,
I've already created the patch, but no one merge it!
I don't know how to create a developer account in apache, it looks like I can't commit to
apache's SVN. Now I've created the patch, but I can't merge it neither!

When I post issues in, there are so many people contact to me, compared to, it feels like codehaus is dead!

> Don't overwrite SVN auth cache
> ------------------------------
>                 Key: MRELEASE-497
>                 URL:
>             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
>            Priority: Critical
>         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:
For more information on JIRA, see:


View raw message