Re: Configuring Authentication: How to specify scm username/password in settings.xml instead of pom.xml

2010-07-26 Thread Marshall Schor
 also, for encryption, read
http://maven.apache.org/guides/mini/guide-encryption.html

-Marshall Schor

On 7/23/2010 3:04 AM, Stefan Cordes wrote:
 Hi!
 On 
 http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html
  

 it is just stated that username/password can be stored in the pom.xml.

 How to specify it in the settings.xml?


 --
 RSC Commercial Services OHG
 Wanheimer Strasse 70, D-40468 Duesseldorf
 Registergericht: Duesseldorf, HRA 12655



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Configuring Authentication: How to specify scm username/password in settings.xml instead of pom.xml

2010-07-25 Thread Anders Hammar
One way of doing this is defining properties in an active profile in
settings.xml and use those properties when configuring the scm-plugin in the
pom. There are othersolutions as well and may depend on your scm.

/Anders

On Fri, Jul 23, 2010 at 09:04, Stefan Cordes dt0...@retail-sc.com wrote:

 Hi!
 On

 http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html

 it is just stated that username/password can be stored in the pom.xml.

 How to specify it in the settings.xml?


 --
 RSC Commercial Services OHG
 Wanheimer Strasse 70, D-40468 Duesseldorf
 Registergericht: Duesseldorf, HRA 12655




Configuring Authentication: How to specify scm username/password in settings.xml instead of pom.xml

2010-07-23 Thread Stefan Cordes
Hi!
On 
http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html
 

it is just stated that username/password can be stored in the pom.xml.

How to specify it in the settings.xml?


--
RSC Commercial Services OHG
Wanheimer Strasse 70, D-40468 Duesseldorf
Registergericht: Duesseldorf, HRA 12655



Re: How to specify SCM username/password for release plugin?

2009-05-04 Thread Baptiste MATHUS
Hi,

In the documentation of the mojo (btw, you didn't say which goal you were
speaking) of the release:prepare for example:

http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html

username/password.

Cheers.

2009/5/1 David Hoffer dhoff...@gmail.com

 How can I specify the username/password to be used by the release plugin in
 the settings.xml file (or other system approach)?  Normally this is set in
 the settings.xml and refereed to elsewhere by it's id but how is this
 refereed by the SCM?

 -Dave




-- 
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !


Re: How to specify SCM username/password for release plugin?

2009-05-04 Thread Gordon Cody
(with appropriate substitutions of course) In our topmost pom for the
project we use:

  scm

developerConnectionscm:svn:https://svnhost/svnrepo/trunk/developerConnection
  /scm

and in the settings.xml (of those allowed to do releases) we put both
server entries:

  servers
server
idlibs-releases/id
usernamethereleaseuser/username
passwordthereleasepassword/password
/server
server
idlibs-snapshots/id
usernamethedeveloperuser/username
passwordthedeveloperpassword/password
/server
  /servers

Regards,
Gord Cody

On Mon, May 4, 2009 at 5:46 AM, Baptiste MATHUS m...@batmat.net wrote:
 Hi,

 In the documentation of the mojo (btw, you didn't say which goal you were
 speaking) of the release:prepare for example:

 http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html

 username/password.

 Cheers.

 2009/5/1 David Hoffer dhoff...@gmail.com

 How can I specify the username/password to be used by the release plugin in
 the settings.xml file (or other system approach)?  Normally this is set in
 the settings.xml and refereed to elsewhere by it's id but how is this
 refereed by the SCM?

 -Dave




 --
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: How to specify SCM username/password for release plugin?

2009-05-04 Thread David Hoffer
Does this support encryption?  We don't want passwords in plan text.  We
really don't want names/passwords in the pom as those are global values, we
really want server names/passwords encrypted and in the settings.xml or
other system location.

we run release:prepare followed by release:perform

-Dave

On Mon, May 4, 2009 at 3:46 AM, Baptiste MATHUS m...@batmat.net wrote:

 Hi,

 In the documentation of the mojo (btw, you didn't say which goal you were
 speaking) of the release:prepare for example:

 http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html

 username/password.

 Cheers.

 2009/5/1 David Hoffer dhoff...@gmail.com

  How can I specify the username/password to be used by the release plugin
 in
  the settings.xml file (or other system approach)?  Normally this is set
 in
  the settings.xml and refereed to elsewhere by it's id but how is this
  refereed by the SCM?
 
  -Dave
 



 --
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !



Re: How to specify SCM username/password for release plugin?

2009-05-04 Thread David Hoffer
How is either server id tied to the SCM?  We too have server id/s but these
are used for artifact deployment login not SCM login.  How can I use these
for SCM login?

-Dave

On Mon, May 4, 2009 at 6:22 AM, Gordon Cody gc...@zafinlabs.com wrote:

 (with appropriate substitutions of course) In our topmost pom for the
 project we use:

  scm
developerConnectionscm:svn:https://svnhost/svnrepo/trunk
 /developerConnection
  /scm

 and in the settings.xml (of those allowed to do releases) we put both
 server entries:

  servers
server
idlibs-releases/id
usernamethereleaseuser/username
passwordthereleasepassword/password
/server
server
idlibs-snapshots/id
usernamethedeveloperuser/username
passwordthedeveloperpassword/password
/server
  /servers

 Regards,
 Gord Cody

 On Mon, May 4, 2009 at 5:46 AM, Baptiste MATHUS m...@batmat.net wrote:
  Hi,
 
  In the documentation of the mojo (btw, you didn't say which goal you were
  speaking) of the release:prepare for example:
 
  http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html
 
  username/password.
 
  Cheers.
 
  2009/5/1 David Hoffer dhoff...@gmail.com
 
  How can I specify the username/password to be used by the release plugin
 in
  the settings.xml file (or other system approach)?  Normally this is set
 in
  the settings.xml and refereed to elsewhere by it's id but how is this
  refereed by the SCM?
 
  -Dave
 
 
 
 
  --
  Baptiste Batmat MATHUS - http://batmat.net
  Sauvez un arbre,
  Mangez un castor !
 

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




Re: How to specify SCM username/password for release plugin?

2009-05-04 Thread Baptiste MATHUS
You want to have a look at this:
http://maven.apache.org/guides/mini/guide-encryption.html
However, this is only available since 2.1.

Btw, we use user/password. Settings.xml is shared by everybody, we just use
something like ${env.m2DeployUser}/${env.m2DeployPwd} and then ask the
developers who have deployment account to specify value for the
corresponding environment variable with their own account credentials. This
way, they're the only one to know their user/pwd. The Settings.xml doesn't
convey any.

Cheers.

2009/5/4 David Hoffer dhoff...@gmail.com

 Does this support encryption?  We don't want passwords in plan text.  We
 really don't want names/passwords in the pom as those are global values, we
 really want server names/passwords encrypted and in the settings.xml or
 other system location.

 we run release:prepare followed by release:perform

 -Dave

 On Mon, May 4, 2009 at 3:46 AM, Baptiste MATHUS m...@batmat.net wrote:

  Hi,
 
  In the documentation of the mojo (btw, you didn't say which goal you were
  speaking) of the release:prepare for example:
 
  http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html
 
  username/password.
 
  Cheers.
 
  2009/5/1 David Hoffer dhoff...@gmail.com
 
   How can I specify the username/password to be used by the release
 plugin
  in
   the settings.xml file (or other system approach)?  Normally this is set
  in
   the settings.xml and refereed to elsewhere by it's id but how is this
   refereed by the SCM?
  
   -Dave
  
 
 
 
  --
  Baptiste Batmat MATHUS - http://batmat.net
  Sauvez un arbre,
  Mangez un castor !
 




-- 
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !


How to specify SCM username/password for release plugin?

2009-05-01 Thread David Hoffer
How can I specify the username/password to be used by the release plugin in
the settings.xml file (or other system approach)?  Normally this is set in
the settings.xml and refereed to elsewhere by it's id but how is this
refereed by the SCM?

-Dave


Re: SCM Username/Password

2008-02-06 Thread Edwin Punzalan
I believe there is a separate UI for the release, have you used that?

On Feb 5, 2008 11:30 AM, deckrider [EMAIL PROTECTED] wrote:

 Hello,

 I want to have the users who add builds to continuum to enter their
 SCM Username/Password.  However this isn't working during the commits
 needed to run the following targets:

 release:prepare release:perform

 We are using subversion, but when it comes time to commit it says
 invalid credentials.

 I don't want to simply check in or otherwise define in public clear
 text these usernames and passwords.

 Thanks in advance!



SCM Username/Password

2008-02-05 Thread deckrider
Hello,

I want to have the users who add builds to continuum to enter their
SCM Username/Password.  However this isn't working during the commits
needed to run the following targets:

release:prepare release:perform

We are using subversion, but when it comes time to commit it says
invalid credentials.

I don't want to simply check in or otherwise define in public clear
text these usernames and passwords.

Thanks in advance!


Re: SCM username/password lookup

2006-01-06 Thread dan tran
any one?

-D


On 1/5/06, dan tran [EMAIL PROTECTED] wrote:


 There are 3 places to look for in this order

   Command line
   settings.xml
   connectionUrl

 However in maven-release-plugin, if user does not provide username
 via command line (ie -Dusername=xyz),
 username is default to system property ${user.name} and by passing
 settings.xml.

 is it a bug?


 -Dan





Re: SCM username/password lookup

2006-01-06 Thread Jesse McConnell
well, it sounds like one to me

On 1/6/06, dan tran [EMAIL PROTECTED] wrote:

 There are 3 places to look for in this order

   Command line
   settings.xml
   connectionUrl

 However in maven-release-plugin, if user does not provide username
 via command line (ie -Dusername=xyz),
 username is default to system property ${user.name} and by passing
 settings.xml.

 is it a bug?


 -Dan




--
jesse mcconnell


RE: SCM username/password lookup

2006-01-06 Thread Brian E. Fox
Might not be a bug in the classic sense because maybe that was the
intention, but certainly not maven like behavior.
+1 for making it use servers section like everything else. 

-Original Message-
From: Jesse McConnell [mailto:[EMAIL PROTECTED] 
Sent: Friday, January 06, 2006 4:07 PM
To: Maven Users List
Subject: Re: SCM username/password lookup

well, it sounds like one to me

On 1/6/06, dan tran [EMAIL PROTECTED] wrote:

 There are 3 places to look for in this order

   Command line
   settings.xml
   connectionUrl

 However in maven-release-plugin, if user does not provide username via

 command line (ie -Dusername=xyz), username is default to system 
 property ${user.name} and by passing settings.xml.

 is it a bug?


 -Dan




--
jesse mcconnell


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: SCM username/password lookup

2006-01-06 Thread Emmanuel Venisse

Yes, i think it's a bug. We must set username to ${user.name} if other places 
don't set it.

Emmanuel

dan tran a écrit :

any one?

-D


On 1/5/06, dan tran [EMAIL PROTECTED] wrote:



There are 3 places to look for in this order

 Command line
 settings.xml
 connectionUrl

However in maven-release-plugin, if user does not provide username
via command line (ie -Dusername=xyz),
username is default to system property ${user.name} and by passing
settings.xml.

is it a bug?


-Dan









-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: SCM username/password lookup

2006-01-06 Thread dan tran
OK, JIRA is on the way

Thank your for all inputs

-D


On 1/6/06, Emmanuel Venisse [EMAIL PROTECTED] wrote:

 Yes, i think it's a bug. We must set username to ${user.name} if other
 places don't set it.

 Emmanuel

 dan tran a écrit :
  any one?
 
  -D
 
 
  On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
 
 
 There are 3 places to look for in this order
 
   Command line
   settings.xml
   connectionUrl
 
 However in maven-release-plugin, if user does not provide username
 via command line (ie -Dusername=xyz),
 username is default to system property ${user.name} and by passing
 settings.xml.
 
 is it a bug?
 
 
 -Dan
 
 
 
 
 


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: SCM username/password lookup

2006-01-06 Thread dan tran
I thought the maven dev folks working very hard not to allow maven-scm from
knowing
anything about maven ( in this case, settings.xml). The prefer way is thru
plugins

is it still true?

-Dan




On 1/6/06, David Hawkins [EMAIL PROTECTED] wrote:

 In the new pure java svn provider (SCM-13), I had it look up the username,
 password, passphrase, etc in the servers of a user's settings.  I
 implemented it so that the server id could be nearly any piece of the
 server
 + url. Afterwards I was thinking it might be better to implement this in a
 generic way so that all scm providers either:
 a.) return a server id to be used to lookup the server and the scm-api
 would assign the server to the ScmProvider.  The provider would then
 fetch
 the username, password, private key, and any other applicable settings.
 b.) passed a reference to the settings object or servers list and let
 the
 provider find the applicable server itself.

 The release plugin has StarTeam specific code which basically looks up the
 auth information from the settings.  If this is a common thing for
 multiple
 providers, we should probably handle it at a higher level than within each
 provider.  Something should definitely be done so that we don't have
 provider specific code in various plugins.

 --David


 - Original Message -
 From: Emmanuel Venisse [EMAIL PROTECTED]
 To: Maven Users List users@maven.apache.org
 Sent: Friday, January 06, 2006 3:23 PM
 Subject: Re: SCM username/password lookup


  Yes, i think it's a bug. We must set username to ${user.name} if other
  places don't set it.
 
  Emmanuel
 
  dan tran a écrit :
  any one?
 
  -D
 
 
  On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
 
 
 There are 3 places to look for in this order
 
   Command line
   settings.xml
   connectionUrl
 
 However in maven-release-plugin, if user does not provide username
 via command line (ie -Dusername=xyz),
 username is default to system property ${user.name} and by passing
 settings.xml.
 
 is it a bug?
 
 
 -Dan
 
 
 
 
 
 
 
  -
  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]




Re: SCM username/password lookup

2006-01-06 Thread Brett Porter
Yes. Anything settings.xml provides should be passed into the SCM API.

- Brett

On 1/7/06, dan tran [EMAIL PROTECTED] wrote:
 I thought the maven dev folks working very hard not to allow maven-scm from
 knowing
 anything about maven ( in this case, settings.xml). The prefer way is thru
 plugins

 is it still true?

 -Dan




 On 1/6/06, David Hawkins [EMAIL PROTECTED] wrote:
 
  In the new pure java svn provider (SCM-13), I had it look up the username,
  password, passphrase, etc in the servers of a user's settings.  I
  implemented it so that the server id could be nearly any piece of the
  server
  + url. Afterwards I was thinking it might be better to implement this in a
  generic way so that all scm providers either:
  a.) return a server id to be used to lookup the server and the scm-api
  would assign the server to the ScmProvider.  The provider would then
  fetch
  the username, password, private key, and any other applicable settings.
  b.) passed a reference to the settings object or servers list and let
  the
  provider find the applicable server itself.
 
  The release plugin has StarTeam specific code which basically looks up the
  auth information from the settings.  If this is a common thing for
  multiple
  providers, we should probably handle it at a higher level than within each
  provider.  Something should definitely be done so that we don't have
  provider specific code in various plugins.
 
  --David
 
 
  - Original Message -
  From: Emmanuel Venisse [EMAIL PROTECTED]
  To: Maven Users List users@maven.apache.org
  Sent: Friday, January 06, 2006 3:23 PM
  Subject: Re: SCM username/password lookup
 
 
   Yes, i think it's a bug. We must set username to ${user.name} if other
   places don't set it.
  
   Emmanuel
  
   dan tran a écrit :
   any one?
  
   -D
  
  
   On 1/5/06, dan tran [EMAIL PROTECTED] wrote:
  
  
  There are 3 places to look for in this order
  
Command line
settings.xml
connectionUrl
  
  However in maven-release-plugin, if user does not provide username
  via command line (ie -Dusername=xyz),
  username is default to system property ${user.name} and by passing
  settings.xml.
  
  is it a bug?
  
  
  -Dan
  
  
  
  
  
  
  
   -
   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]
 
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



SCM username/password lookup

2006-01-05 Thread dan tran
There are 3 places to look for in this order

  Command line
  settings.xml
  connectionUrl

However in maven-release-plugin, if user does not provide username
via command line (ie -Dusername=xyz),
username is default to system property ${user.name} and by passing
settings.xml.

is it a bug?


-Dan