db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henning P. Schmiedehausen" <...@intermeta.de>
Subject Re: Deployment to repository [was" [SOURCE] Issue #TRQS217 modified]
Date Wed, 25 Aug 2004 12:41:43 GMT
Scott Eade <seade@backstagetech.com.au> writes:

>Thanks Henning, this sounds really good.  I know it is OT, but would you 
>mind listing for me the properties that I need to set to make this work.

>Maven tells me that I need:

>    maven.username

I have

maven.ssh.args=-o ForwardX11=false

in my local ~/build.properties because I need them all the time.

The project itself then gets 


in its project.properties.

>It tries to deploy to ibiblio so I suppose I have to tell it where the 
>repository is.  Is it the various maven:artifact settings that I need to 
>set?  If you can send me a sanitised copy of what you have it will save 
>me some time.

Change the distribution lines in project.xml


You can take a look at the current Turbine 2.3 tree. There I did all
the changes necessary for deploying to the apache site.
>My intention is to deploy 3.1.1-rc1 of generator, maven-plugin and 
>runtime and then hold a release vote.  For the release I will have to 
>look at creating and deploying the actual distributions (signing, 
>mirroring, etc.)

Goes just like the RCs. I can help you with signing; i already did
this for Turbine 2.3.

You should be able to log into www.apache.org without it having to
prompt for a password by using ssh-keys. If you don't have a local
key, this is how you do it:

On your local machine, you run

$ ssh-keygen -b 1024 -d

When it asks you, where to store the keys, you simple press return.
When it asks you for a pass-phrase, you enter a secret message which
should be treated like a password.

Now you should have a file called id_dsa.pub in the .ssh subdirectory
on your local machine. This is your public key id. You copy this file
to www.apache.org. On www.apache.org, you also create a .ssh
subdirectory in your home (you probably already have one).

Append the id_dsa.pub file to ~/.ssh/authorized_keys2 
(use cat id_dsa.pub >> ~/.ssh/authorized_keys2 )

Now log out again. On your local computer, run

ssh-add -l

On any reasonably current Linux distribution, this should display

The agent has no identities.

If it tells you "could not contact the secure shell agent", then you
must run a subshell with "ssh-agent /bin/bash" first.

Almost there. Now run


This prompts for a login:

Enter passphrase for <home directory>/.ssh/id_dsa:

Now enter your pass phrase. 

ssh-add -l should now display a few lines similar to:

1024 27:7d:8d:61:70:c0:36:c9:c1:a8:e8:62:d5:95:17:ee /home/henning/.ssh/id_dsa (DSA)

Try logging into www.apache.org using slogin. This should work without
a password prompt.

A, I forgot, you should have some sort of unixoid system. :-)
Windows; well, with cygwin this should go just like this. 
Regular Windows, gee. No idea. 


Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/

RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for hire
   Linux, Java, perl, Solaris -- Consulting, Training, Development

"Fighting for one's political stand is an honorable action, but re-
 fusing to acknowledge that there might be weaknesses in one's
 position - in order to identify them so that they can be remedied -
 is a large enough problem with the Open Source movement that it
 deserves to be on this list of the top five problems."
                       -- Michelle Levesque, "Fundamental Issues with
                                    Open Source Software Development"

To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message