You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lenik (JIRA)" <ji...@codehaus.org> on 2009/10/26 07:22:26 UTC
[jira] Created: (MRELEASE-497) Don't overwrite SVN auth cache
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
Priority: Critical
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
[jira] Updated: (MRELEASE-497) Don't overwrite SVN auth cache
Posted by "Lenik (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lenik updated MRELEASE-497:
---------------------------
Attachment: no-auth-cache.patch
A patch to add --no-auth-cache option to svn command line.
unit test passed.
> 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
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-497) Don't overwrite SVN auth cache
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MRELEASE-497) Don't overwrite SVN auth cache
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated MRELEASE-497:
----------------------------------
Fix Version/s: 2.1
Assignee: Olivier Lamy
> 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
[jira] Issue Comment Edited: (MRELEASE-497) Don't overwrite SVN
auth cache
Posted by "Lenik (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197781#action_197781 ]
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 bugs.eclipse.org, there are so many people contact to me, compared to jira.codehaus.org, it feels like codehaus is dead!
> 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
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-497) Don't overwrite SVN auth cache
Posted by "Lenik (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197781#action_197781 ]
Lenik commented on MRELEASE-497:
--------------------------------
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 bugs.eclipse.org, there are so many people contact to me, compared to jira.codehaus.org, it feels like codehaus is dead!
> 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
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira