Hi Phil, On Tue, 2005-05-24 at 05:06 +0000, [EMAIL PROTECTED] wrote: > - > - > ###################################################################### > -# Apache Central Repository > +# Deployment Repository Settings > +# > +# 'apache' is the mirrored public release repository > +# 'apachecvs' is the internal repository for snapshots
Could you explain what you mean by "Deployment repository"? Do you mean that jar:deploy performs some parts of steps 5-8 in this document? http://jakarta.apache.org/commons/releases/release.html > +# > +# By default, deployment is to the internal apache repository. > +# To deploy to the mirrored distribution repository, use > +# > +# maven -Dmaven.repo.list=apache jar:deploy > +# > +# The following properties need to be set in local build.properties: > +# > +# maven.repo.apache.username - apache user name > +# maven.repo.apache.privatekey - path to local private ssh key > +# maven.repo.apache.passphrase - passphrase for private ssh key I believe that maven.repo.apache.privatekey is not needed if your private key is in the default location ~/.ssh/id_dsa? And that the passphrase is not needed if your key has no passphrase (yes, keys should)? When pushing out websites I set maven.username but not maven.privatekey and things work ok.. Why is the name "apachecvs" used, when we are moving away from cvs? May I suggest maven.repo.apache.releases=... maven.repo.apache.snapshots=... instead of maven.repo.apache maven.repo.apachecvs Thanks for this. Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
