You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by ps...@apache.org on 2005/05/24 07:06:06 UTC
svn commit: r178077 -
/jakarta/commons/proper/commons-build/trunk/project.properties.sample
Author: psteitz
Date: Mon May 23 22:06:04 2005
New Revision: 178077
URL: http://svn.apache.org/viewcvs?rev=178077&view=rev
Log:
Updated sample deployment repository settings.
Modified:
jakarta/commons/proper/commons-build/trunk/project.properties.sample
Modified: jakarta/commons/proper/commons-build/trunk/project.properties.sample
URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/project.properties.sample?rev=178077&r1=178076&r2=178077&view=diff
==============================================================================
--- jakarta/commons/proper/commons-build/trunk/project.properties.sample (original)
+++ jakarta/commons/proper/commons-build/trunk/project.properties.sample Mon May 23 22:06:04 2005
@@ -18,16 +18,42 @@
######################################################################
maven.changelog.factory=org.apache.maven.svnlib.SvnChangeLogFactory
-
-
######################################################################
-# Apache Central Repository
+# Deployment Repository Settings
+#
+# 'apache' is the mirrored public release repository
+# 'apachecvs' is the internal repository for snapshots
+#
+# 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
+#
######################################################################
-maven.repo.central=www.apache.org
-maven.repo.central.directory=/www/www.apache.org/dist/java-repository
-maven.remote.group=apcvs
-
-
+# Repository to deploy to - internal apache repo
+maven.repo.list=apachecvs
+
+# Repository to deploy snapshots
+maven.repo.apachecvs=scp://cvs.apache.org
+maven.repo.apachecvs.directory=/www/cvs.apache.org/repository
+maven.repo.apachecvs.username=${maven.repo.apache.username}
+maven.repo.apachecvs.privatekey=${maven.repo.apache.privatekey}
+maven.repo.apachecvs.passphrase=${maven.repo.apache.passphrase}
+maven.repo.apachecvs.group=apcvs
+
+# Release repository - rsynched to mirrors
+maven.repo.apache=scp://people.apache.org
+maven.repo.apache.directory=${pom.distributionDirectory}
+maven.repo.apache.group=maven
+maven.repo.apache.username=${maven.repo.apache.username}
+maven.repo.apache.privatekey=${maven.repo.apache.privatekey}
+maven.repo.apache.passphrase=${maven.repo.apache.passphrase}
######################################################################
# JUnit Testing
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: svn commit: r178077 - /jakarta/commons/proper/commons-build/trunk/project.properties.sample
Posted by Phil Steitz <ph...@gmail.com>.
On 5/24/05, Simon Kitching <sk...@apache.org> wrote:
> Hi Phil,
>
> On Tue, 2005-05-24 at 05:06 +0000, psteitz@apache.org 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?
Yes, exactly. If you have things set up correctly, you don't have to
manually copy the jars, poms, etc. jar:deploy does it for you using
scp. I just committed a change to the release docs explaining this
(well, basically just pointing here ;-)
> 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?
I don't know, though this sounds reasonable. No default is mentioned here:
http://maven.apache.org/reference/plugins/artifact/properties.html
And that the
> passphrase is not needed if your key has no passphrase (yes, keys
> should)?
I know this is true (though of course I should not ;-)
>
> When pushing out websites I set maven.username but not maven.privatekey
> and things work ok..
I think that JCSH *requires* a key (unless I misunderstood Brett)
>
>
> Why is the name "apachecvs" used, when we are moving away from cvs?
> May I suggest
> maven.repo.apache.releases=...
> maven.repo.apache.snapshots=...
We think alike; but the names below are in widespread use (like the
group name "apcvs") and I am told there is a desire to maintain
consistency
> instead of
> maven.repo.apache
> maven.repo.apachecvs
>
>
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: svn commit: r178077 - /jakarta/commons/proper/commons-build/trunk/project.properties.sample
Posted by Brett Porter <br...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Simon Kitching wrote:
|
|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)?
Both correct in most cases. user.home is not what you expect on cygwin
though which trips some people up.
|
|When pushing out websites I set maven.username but not maven.privatekey
|and things work ok..
Websites use a different mechanism to artifact deployment (at the moment).
|
|
|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
+1
- - Brett
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCkr+EOb5RoQhMkRMRArdUAJ0Wllf27hCAg3ZXFwKbDe/loP8tNgCgqgd+
IqW0LGHx070/1TJawkHXiJE=
=os52
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: svn commit: r178077 -
/jakarta/commons/proper/commons-build/trunk/project.properties.sample
Posted by Simon Kitching <sk...@apache.org>.
Hi Phil,
On Tue, 2005-05-24 at 05:06 +0000, psteitz@apache.org 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org