Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: repository@apache.org
Received-SPF: pass (hermes.apache.org: domain of brett.porter@gmail.com
 designates 64.233.184.206 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=sY+dBriRGosNpKNmxEP98n/tm4Y7KOwfnkx7hKdfs4HKelTiHQL+9oOfentOD+nWBGozfXJ83Jma/al8Td3fONJ8iJV0qdiwSqPTUaKdDySjnucg0Dr0fvqYMFZo9k3pW2qGSIXGaXF52Yi+NSx4cjAJE1ujG9v6EWCf0CV2Kto=
Message-ID: <9e3862d805052214572e1823c9@mail.gmail.com>
Date: Mon, 23 May 2005 07:57:43 +1000
From: Brett Porter <brett.porter@gmail.com>
Reply-To: Brett Porter <brett.porter@gmail.com>
To: repository@apache.org
Subject: Re: Maven project.properties settings
Cc: phil@steitz.com
In-Reply-To: <42909987.6000606@steitz.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <42909987.6000606@steitz.com>

Hi Phil,

I've named them "apache" and "apachecvs". It would be good if we can
be consistent on this so you only need to set one set of properties.
It's helpful to have "apache" in the name for those that might be
deploying to other hardware with the same install.

In the sample, I usually add the required properties commented out
(.username, .privateKey). For apachecvs, I set them to their "apache"
equivalents since it is the same hardware. This just means setting 2
or 3 properties in ~/build.properties.

Here's an example (though you don't need to use distributionSite and
distributionDirectory variables):
http://svn.apache.org/viewcvs.cgi/maven/maven-1/jelly-tags/trunk/project.pr=
operties?rev=3D155888&view=3Dmarkup

When it comes to deployment, I recommend just setting
-Dmaven.repo.list=3Dapache on the command line.

Final thing: your maven.remote.group below should be formed as a
repository property.

Thanks for your work on this.

Cheers,
Brett

On 5/23/05, Phil Steitz <phil@steitz.com> wrote:
> We are in process of updating the j-c docs on cutting releases and I
> want to include instructions on how to release jars using maven
> jar:deploy.  I would like to add something like the following to
> build.properties.sample and refer to it in the docs.
>=20
> Can someone pls verify that these settings are correct and that,
> assuming maven.repo.external.username (or internal for snapshots) is set
> on the command line or in build.properties, using maven jar:deploy will
> work given this setup.  Since we don't seem to have ssh any longer to
> www, does this mean that the "release" repo below will not work?
>=20
> thx,
>=20
> Phil
>=20
> ######################################################################
> # Apache internal Repository
> ######################################################################
> maven.repo.internal=3Dscp://cvs.apache.org
> maven.repo.internal.directory=3D/www/cvs.apache.org/repository
> maven.repo.internal.group=3Dapcvs
>=20
> ######################################################################
> # Apache Distribution Repository
> ######################################################################
> maven.repo.release=3Dwww.apache.org
> maven.repo.release.directory=3D/www/www.apache.org/dist/java-repository
> maven.remote.group=3Dapcvs
>=20
> ######################################################################
> # List of remote repositories to deploy artifacts to
> # Add ",release" to release to the mirrored release repo
> ######################################################################
> maven.repo.list=3D internal
>