Re: SCM username/password lookup
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
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
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
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
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
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
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]
