Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.5.1
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- is blocked by
-
SCM-1011 Do not set --non-interactive for SVN provider by default
-
- In Progress
-
-
-
- Closed
-
- is related to
-
-
- Open
-