There is no alternate -- you must put the name & password in the file. If this is a significant problem for your organization, then I'd suggest that you write the code to handle encrypted passwords in settings.xml and contribute it back to the Maven development effort.
You're not the only person who has been unhappy with this limitation. But in my opinion, the file system security on that file should prevent just about anyone from accessing it except the proper user, right? So is this really a problem, or just a general "best practices" argument about not storing passwords in plaintext? And yes, the settings.xml file should be located in ~/.m2/, as specified in the Mergere Maven book in section 2.1. Wayne On 6/1/06, Vikramm <[EMAIL PROTECTED]> wrote:
Thanks for help. Yes, I am behind a web proxy. The settings.xml needs username & password. For security reasons am not able to give this. Is there alternate way to get this done. Also, the settings.xml file should be kept in ~/.m2/ folder ? Thanks. -- View this message in context: http://www.nabble.com/Installing+-+running+Maven+2.0.4-t1713822.html#a4670574 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
