I don't think they misunderstood what you were asking for, you just seem to have different grasps on the matter, thus a misunderstanding. To your concern: What you read seems to be right, user/password are client specific(pom is project specific, they are pretty public) settings, you can/should put those into settings.xml(this file is local in most cases, so pretty private) in the section settings/servers/server(http://maven.apache.org/settings.html). Most SCM-Providers will be able to authenticate using the settings made there. You link the server-element (in the settings.xml) to the scm-element(in the pom) with the id-element of server(I'm sure you'll find out how). The other guys eventually knew this stuff, took it for given and wanted to hint(you asked for best practice) that you can encrypt the passwords now stored in your settings.xml(for security reasons). Hoping I did understand you correctly and best regards.
-----Ursprüngliche Nachricht----- Von: Eric Kolotyluk [mailto:eric.koloty...@gmail.com] Gesendet: Mittwoch, 15. August 2012 21:55 An: Maven Users List Betreff: Re: Best Practices for Passwords and Usernames OK, now I see why I cannot find any documentation for what I want. 3 different people misunderstood what I was asking for. I must be asking it wrong, or thinking about it wrong. Basically, when I have a situation where I have some username and password for the scm plugin, where do I store such information, and how do I configure the scm plugin, the release plugin, etc. to find that information? I was reading http://www.mosabuam.com/2009/10/company-super-pom-a-maven-practice and he says to put the passwords in your settings.xml file, but I have no idea what his intent is without any tangible example. Cheers, Eric --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
