[
http://jira.codehaus.org/browse/CONTINUUM-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179187#action_179187
]
Wendy Smoak commented on CONTINUUM-2251:
----------------------------------------
Is this with Subversion? Did you check the 'use cached credentials if
available' checkbox when you added the project in step 1?
My guess is it's probably using cached credentials.
I don't think it needs to prompt -- there are already fields on the 'prepare
release' form that the user should fill in.
Not sure this is a bug, it's just how Subversion works if you don't explicitly
tell it _not_ to cache credentials.
> Releasing secured projects will not prompt username/password needed with SCM
> Username and SCM Password not provided on release:perform goals
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-2251
> URL: http://jira.codehaus.org/browse/CONTINUUM-2251
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.3
> Reporter: Marecor Baclay
>
> Steps to replicate:
> 1. Add a secured project
> 2. Build the project
> 3. Release the project
> - in release:prepare, do not provide values in SCM Username and SCM Password
> actual result:
> release:perform goal was successful.
> It should not execute the release:perform goal, thus it must prompt a message
> asking for the SCM Username and SCM Password.
--
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
