Return-Path: 
 <dev-return-126304-apmail-commons-dev-archive=commons.apache.org@commons.apache.org>
X-Original-To: apmail-commons-dev-archive@www.apache.org
Delivered-To: apmail-commons-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C994A4A53
	for <apmail-commons-dev-archive@www.apache.org>;
 Mon, 16 May 2011 00:28:17 +0000 (UTC)
Received: (qmail 9337 invoked by uid 500); 16 May 2011 00:28:17 -0000
Delivered-To: apmail-commons-dev-archive@commons.apache.org
Received: (qmail 9255 invoked by uid 500); 16 May 2011 00:28:17 -0000
Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@commons.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@commons.apache.org>
List-Post: <mailto:dev@commons.apache.org>
List-Id: <dev.commons.apache.org>
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Delivered-To: mailing list dev@commons.apache.org
Received: (qmail 9247 invoked by uid 99); 16 May 2011 00:28:17 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2011 00:28:17 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.220.171 as permitted sender)
Received: from [209.85.220.171] (HELO mail-vx0-f171.google.com)
 (209.85.220.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2011 00:28:10 +0000
Received: by vxc40 with SMTP id 40so3415230vxc.30
        for <dev@commons.apache.org>; Sun, 15 May 2011 17:27:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:content-type:content-transfer-encoding;
        bh=f0rbPRbQPj8X0Vt6HAj1wFd5ffzgCtwiPeaylvHOh4M=;
        b=XeUCsvlhBRfMyXfozszR2MOMGOXsTStc0ItmZVErc9wpzFwZ7WfsqRvEGlb7KVsL8Y
         1NINTWrTb5kQayURzvP3ciqGv9EYS30zRAZehvXvjyDD8hXFXlvW0FQRAlG8IXESav7c
         TtAGgOUnb2jL+G+xwxCIk6jylMEdj2sJWBia0=
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=n3Tfh8bmS6vS2hKtfpzChCZWdhaDDipVfC3q93OjClBOqwYMee5Z53I91lk26lntOi
         Cp/mhTCl+pX9kvekDNehWFuVgf1JmunCscjhkFSWJhn2Fvdk+gRx7yeLvkukw0WzFG3G
         ebotT7T1X+yE6aCG4gNv7r2+gdpUuvyautVG4=
MIME-Version: 1.0
Received: by 10.220.169.18 with SMTP id w18mr1156438vcy.74.1305505669524; Sun,
 15 May 2011 17:27:49 -0700 (PDT)
Received: by 10.220.16.211 with HTTP; Sun, 15 May 2011 17:27:49 -0700 (PDT)
In-Reply-To: <BANLkTi=_z0rh8-LLOpMoWS1QS943co0nDw@mail.gmail.com>
References: <BANLkTimtC7T=w2kzwHG_jKtxvCE81bXmLQ@mail.gmail.com>
	<BANLkTi=_z0rh8-LLOpMoWS1QS943co0nDw@mail.gmail.com>
Date: Mon, 16 May 2011 01:27:49 +0100
Message-ID: <BANLkTikjMOHxsEY=MBUEKw+xa=bWaw79kw@mail.gmail.com>
Subject: Re: [ALL] Binary archives without -bin incompatible with latest
 assembly plugin
From: sebb <sebbaz@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 16 May 2011 00:21, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> On Sat, May 14, 2011 at 5:03 PM, sebb <sebbaz@gmail.com> wrote:
>> The assembly descriptor id (e.g. <id>src</id>) is automatically
>> appended to the name of the archives created by the assembly plugin.
>>
>> Up until version 2.2-beta-4 of the plugin, the <id> tag was allowed to
>> be empty, but with 2.2 this changed [1] - the id must now be
>> not-empty.
>> This means that for example the binary archives will have -bin
>> appended to the archive name.
>>
>> There is a configuration item that can be used to suppress the suffix:
>> =A0 =A0<appendAssemblyId>false</appendAssemblyId>
>> However this suppresses the suffix for both bin and src (i.e. they
>> then have the same name), and it does not appear to be possible to
>> suppress the suffix only for the binary archives.
>>
>> Therefore I think we should standardise on -bin (and -src) suffixes
>> for the archives (we cannot stay on assembly 2.2-beta4 forever).
>>
>> This means ensuring that the appropriate property is set for the
>> commons download plugin:
>>
>> =A0 =A0 =A0 =A0<commons.binary.suffix>bin</commons.binary.suffix>
>> =A0 =A0 =A0 =A0<commons.release.2.binary.suffix>bin</commons.release.2.b=
inary.suffix>
>
> The default values for these in commons-parent is "-bin" - so there is
> no need to set these in any component poms. The only reason these
> binary suffix parameters were ever used was for pre-maven releases
> that didn't have a suffix so that the download page could be correctly
> generated.

Ah, I understand now. I'd not noticed that these were overriding the
parent parameters.

I can therefore remove

<commons.binary.suffix>

from Commons Net. The other will have to remain as the 1.4.1 archives
don't have the -bin suffix.

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