You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by ak...@apache.org on 2005/06/27 20:03:15 UTC
svn commit: r202023 -
/directory/protocol-providers/kerberos/trunk/project.properties
Author: akarasulu
Date: Mon Jun 27 11:03:14 2005
New Revision: 202023
URL: http://svn.apache.org/viewcvs?rev=202023&view=rev
Log:
not everyone uses a ssh key with repo
Modified:
directory/protocol-providers/kerberos/trunk/project.properties
Modified: directory/protocol-providers/kerberos/trunk/project.properties
URL: http://svn.apache.org/viewcvs/directory/protocol-providers/kerberos/trunk/project.properties?rev=202023&r1=202022&r2=202023&view=diff
==============================================================================
--- directory/protocol-providers/kerberos/trunk/project.properties (original)
+++ directory/protocol-providers/kerberos/trunk/project.properties Mon Jun 27 11:03:14 2005
@@ -17,7 +17,6 @@
maven.repo.apachecvs=scp://cvs.apache.org
maven.repo.apachecvs.directory=/www/cvs.apache.org/repository
maven.repo.apachecvs.group=directory
-maven.repo.apachecvs.privatekey=${user.home}/.ssh/id_rsa
# User must specify:
# maven.repo.apachecvs.username=
Re: svn commit: r202023 - /directory/protocol-providers/kerberos/trunk/project.properties
Posted by Alex Karasulu <ao...@bellsouth.net>.
Enrique Rodriguez wrote:
> Regarding this commit, is it the case that leaving in the 'privatekey'
> line *forces* users to use ssh keys? To clarify, the 'privatekey'
> setting should go only in personal build.properties? I just want to
> clarify since I've done this in a number of places, I think.
>
Well props in the project should just not presume how people work. I
personally use the keys and using it is certainly safer. I think it
should go into the build.properties file.
>>
>> Modified:
>> directory/protocol-providers/kerberos/trunk/project.properties
>>
>> Modified: directory/protocol-providers/kerberos/trunk/project.properties
>> URL:
>> http://svn.apache.org/viewcvs/directory/protocol-providers/kerberos/trunk/project.properties?rev=202023&r1=202022&r2=202023&view=diff
>>
>
snip
>> -maven.repo.apachecvs.privatekey=${user.home}/.ssh/id_rsa
>
Re: svn commit: r202023 - /directory/protocol-providers/kerberos/trunk/project.properties
Posted by Enrique Rodriguez <en...@gmail.com>.
Regarding this commit, is it the case that leaving in the 'privatekey'
line *forces* users to use ssh keys? To clarify, the 'privatekey'
setting should go only in personal build.properties? I just want to
clarify since I've done this in a number of places, I think.
Enrique
akarasulu@apache.org wrote:
> Author: akarasulu
> Date: Mon Jun 27 11:03:14 2005
> New Revision: 202023
>
> URL: http://svn.apache.org/viewcvs?rev=202023&view=rev
> Log:
> not everyone uses a ssh key with repo
>
> Modified:
> directory/protocol-providers/kerberos/trunk/project.properties
>
> Modified: directory/protocol-providers/kerberos/trunk/project.properties
> URL: http://svn.apache.org/viewcvs/directory/protocol-providers/kerberos/trunk/project.properties?rev=202023&r1=202022&r2=202023&view=diff
> ==============================================================================
> --- directory/protocol-providers/kerberos/trunk/project.properties (original)
> +++ directory/protocol-providers/kerberos/trunk/project.properties Mon Jun 27 11:03:14 2005
> @@ -17,7 +17,6 @@
> maven.repo.apachecvs=scp://cvs.apache.org
> maven.repo.apachecvs.directory=/www/cvs.apache.org/repository
> maven.repo.apachecvs.group=directory
> -maven.repo.apachecvs.privatekey=${user.home}/.ssh/id_rsa
>
> # User must specify:
> # maven.repo.apachecvs.username=
>
>
>