On Wed, August 15, 2012 5:11 pm, Eric Kolotyluk wrote: >> > After visiting http://www.simpligility.com/ I was not sure where to go > next for something relevant to this discussion. Did you have a more > specific URL?
No... this is just where I blog my technical stuff now so newer stuff will be there.. > We are using Perforce for our SCM. > > So, what I am currently doing is creating a profile called "user" in my > local settings.xml file, and in that profile I set the password and > username properties, then I activate that profile. It seems to work fine > for me and it fairly straightforward to document and explain to people. > Then in our corporate POM I reference those password and username > properties in the scm and p4maven plug-in configurations. Does what I am > doing makes sense, or is there a better way to do it? The general idea > is that all personal information stays in a person's personal > settings.xml file. Thats what I was alluding this. Sounds good to me. > I considered using environment variables as you suggested, Manfred, but > somehow keeping all Maven stuff in a personal settings.xml file seem > easier to document. I agree.. I just mentioned it as an alternative.. specifically it can be useful for CI servers.. > I understand the vulnerability of putting any passwords or secret > information in clear-text in a file, but security always needs to be > balanced with complexity and conveniences. I will have to read up more > on all the password protection schemes others have pointed out, but they > do seem more complicated. Yes.. they are a pita to use especially if you have policies that require regular password changes.. > Anyway, things are becoming more clear to me, but much of this stills > seems like another dark art aspect of Maven :-) Haha... its not that complicated is it? You seem to be mastering it just fine ;-) manfred --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
