[ 
https://issues.apache.org/jira/browse/MNG-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224500#comment-15224500
 ] 

Konrad Windszus edited comment on MNG-4099 at 4/4/16 4:58 PM:
--------------------------------------------------------------

Can you add stronger hint on this in 
http://maven.apache.org/guides/mini/guide-encryption.html? 

Currently it just says: Since Maven 3.2.1 the password is an optional argument.
This should be strong recommendation like: Since Maven 3.2.1 the password 
should no longer be provided as argument to prevent issues with the bash 
history and the decoding of special characters.

At least in the tips section this should be explicitly mention, but preferably 
also in the How-Tos it should be clarified.


was (Author: kwin):
Can you add a hint on this in 
http://maven.apache.org/guides/mini/guide-encryption.html? At least in the tips 
section but preferably also in the How-Tos (with a hint that this is only 
supported since Maven 3.2.1)?

> Password encryption CLI switches should prompt for password if missing
> ----------------------------------------------------------------------
>
>                 Key: MNG-4099
>                 URL: https://issues.apache.org/jira/browse/MNG-4099
>             Project: Maven
>          Issue Type: Improvement
>          Components: Command Line
>    Affects Versions: 2.1.0
>            Reporter: Mark Hobson
>            Assignee: Robert Scholte
>            Priority: Trivial
>             Fix For: 3.2.1
>
>
> The -emp and -ep CLI switches should prompt for a password if the user omits 
> it.  This would help to avoid having to escape shell characters in strong 
> passwords.
> Note that the docs mention that these switches prompt for a password when 
> they do not:
> http://maven.apache.org/guides/mini/guide-encryption.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to