[ https://issues.apache.org/jira/browse/MRELEASE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16314542#comment-16314542 ]
Duncan Paterson commented on MRELEASE-890: ------------------------------------------ If prompts are not the way to go, a dry-run of `release:prepare` should attempt to connect and authenticate if necessary with the repo. As is now, folks can dry run without problems, just to error out on release:perform because of missing authentication data. > Prompt for usernames and passwords when running interactively > ------------------------------------------------------------- > > Key: MRELEASE-890 > URL: https://issues.apache.org/jira/browse/MRELEASE-890 > Project: Maven Release Plugin > Issue Type: Improvement > Affects Versions: 2.5.1 > Reporter: Karl M. Davis > Priority: Critical > > I've been using the release plugin for years now, and also supporting a lot > of other folks using it. > It occurred to me today, that one of the most common sources of frustration > and problems with the release plugin has been authentication: either users > never added {{<server/>}} entries to their {{settings.xml}} or their password > expired and they forgot to update it. Looking back... this has probably been > the cause of around half of all the troubleshooting I've helped folks with. > I think it'd really help the first-run experience for folks if the release > plugin prompted users for their authentication credentials when they're > needed: if they're missing in the {{settings.xml}} and if authentication > failures are encountered. (Only when running interactively, of course.) > I imagine a lot of other folks' experience here might mirror mine, especially > in Windows domain environments with obnoxious password expiration policies. > Even if passwords aren't expiring, though, it seems like I'm setting up a > development environment on a new machine for myself or someone else about > once a month. And the {{settings.xml}} authentication credentials are an > oft-overlooked step. -- This message was sent by Atlassian JIRA (v6.4.14#64029)