If you do it this way, it will be in your shell history file
and also show up in the process list. The true way to deal
with secure passwords is to prompt for them, which I have
seen other maven plugins do.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=254624
You can always run maven with the parameter
-Dmaven.sourceforge.password=xxxx, eg:
maven -Dmaven.sourceforge.password=xxxx sourceforge:deploy-dist
This way your password is never stored in a file
Logged In: YES
user_id=407536
If you do it this way, it will be in your shell history file
and also show up in the process list. The true way to deal
with secure passwords is to prompt for them, which I have
seen other maven plugins do.