db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Eade <se...@backstagetech.com.au>
Subject Re: Deployment to repository [was" [SOURCE] Issue #TRQS217 modified]
Date Thu, 26 Aug 2004 07:42:58 GMT
Excellent.

Thanks for going into so much details below - unfortunately I already 
had my authorized_keys set up so a little of your effort was somewhat 
wasted (though I am sure the information will be useful to others who 
follow).  The trick for Windows with putty (for ssh/scp) is to set up 
maven.scp.executable and maven.ssh.executable in build properties as 
detailed on 
http://maven.apache.org/reference/plugins/site/properties.html (though I 
had to use absolute paths to the executables) - this and the other 
properties and POM elements you provided below has got it working for me.

I have deployed torque-gen-3.1.1-rc1.jar and torque-3.1.1-rc1.jar, but I 
cannot deploy the plugin because of a permission problem.  It seems that 
the directory /x1/www/www.apache.org/dist/java-repository/torque/plugins 
doesn't have group write access and hence I cannot write the jar file 
for the plugin.  Since you are the owner you will be able to add group 
write access for this directory.

Let me know when you are done and I will upload the plugin.  I will also 
commit the last changes to the various properties and POM files and tag RC1.

BTW: I recall a while back you expressing some caution about using 
site:deploy / site:sshdeploy - is this caution still warranted or are 
you happier with these now that maven 1.0 has been released?

Thanks,

Scott

-- 
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au



Henning P. Schmiedehausen wrote:

>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.username=henning
>maven.ssh.args=-o ForwardX11=false
>
>in my local ~/build.properties because I need them all the time.
>
>The project itself then gets 
>
>maven.repo.remote=http://www.ibiblio.org/maven/,http://www.apache.org/dist/java-repository/
>maven.remote.group=apcvs
>
>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
>
><distributionSite>www.apache.org</distributionSite>
><distributionDirectory>/www/www.apache.org/dist/java-repository/</distributionDirectory>
>
>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
>
>ssh-add
>
>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. 
>
>	Regards
>		Henning
>
>  
>



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


Mime
View raw message