Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of antonio.petrelli@gmail.com
 designates 209.85.161.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=GLARMygFlzyeRNfuEhgU9zTgfdrqvo2PAWxnxngueKMGxAzoWss/guvyTc+b9mqttF
         7BO9lExfIH7PG1zOPaZFgDVEZfBjj12bexWLEVAnSGN9WSxQ9XDfEmxpbp2n+niBRVPq
         sLTrrs8u4C2OXSn3apOc2bxDfNmDvfy8K3QlU=
MIME-Version: 1.0
In-Reply-To: <4CD30BA6.8030504@schor.com>
References: <4CD30BA6.8030504@schor.com>
Date: Thu, 4 Nov 2010 20:46:56 +0100
Message-ID: <AANLkTikeY5jq33qxXBoN1FzYJRAiqYEOEVJ3nqbcNiUs@mail.gmail.com>
Subject: Re: Best practice re: releasing large assembly artifacts
From: Antonio Petrelli <antonio.petrelli@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2010/11/4 Marshall Schor <msa@schor.com>:
> Now, we are trying to better align with the Maven way, and are using Nexu=
s. =A0The
> default for assemblies will attach these 16 mb things as artifacts of the
> aggregation project, and mvn release:perform will put them into the Nexus
> repository.
>...
> Is this OK for these big assemblies (both binary and source)? =A0I would =
also copy
> these to the Apache distribution spot, to have them automatically mirrore=
d, in
> addition. =A0Is this the right approach?

IMHO deploying assemblies in a Maven repository is entirely optional,
since other developers rarely take these artifacts as a dependency.
IOW, do it if you need it.

> I experimented with marking the binary assembly with the configuration
> <attach>false</attach> - this works, and prevents it from going up to Nex=
us (and
> then on to Maven central), but has the bad side effect of preventing the
> maven-gpg-plugin from signing that artifact. =A0This is because the maven=
 gpg
> plugin only signs "attached" artifacts.

There's another way, that I use with Tiles and Velocity: skip the deploy
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#skip
and, in the deploy phase, I use Wagon plugin, with some tricks
(install signatures in local repository, copy from local repository
installed artifacts to target folder), to upload assemblies to their
final place.
You can see it working here:
http://svn.eu.apache.org/repos/asf/tiles/framework/trunk/assembly/pom.xml
See the "apache-release" profile.

HTH
Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org