Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of baerrach@gmail.com designates
 209.85.221.185 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=clUot0b2fWoIKMpD96qyuWZ5L9oD7AWoa4WFy93eedJZjfaa0uTVApbIMxKwJHeH6L
         2GsnVJbVHaBegQD3r/tjk4zUOhLWR2hejecX+DUwHP0ACDwsFri6ggc7ApAvmWLDV4Za
         WSE2X74hUTAvPpdAx9mpUN/dhaMg3WqA1F+Dc=
MIME-Version: 1.0
In-Reply-To: <eb0f802d0906041443m3ed20fe1jc0c7f54770d55a74@mail.gmail.com>
References: <f6b307f10906022300w1cbaeea5v60e5bfbbebf89a3f@mail.gmail.com>
	 <4A26EFA4.9070309@udo.edu>
	 <262c6c680906031510r2b7fc779m52cee7dc08c5037b@mail.gmail.com>
	 <4A2815E8.1080306@udo.edu>
	 <eb0f802d0906041443m3ed20fe1jc0c7f54770d55a74@mail.gmail.com>
Date: Fri, 5 Jun 2009 09:18:11 +0930
Message-ID: <f6b307f10906041648g3f0c47c6h556d35c796e5ee50@mail.gmail.com>
Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.7
From: Barrie Treloar <baerrach@gmail.com>
To: Maven Developers List <dev@maven.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 5, 2009 at 7:13 AM, Brian Fox <brianf@infinity.nu> wrote:
> On Thu, Jun 4, 2009 at 11:43 AM, Benjamin Bentmann <
> benjamin.bentmann@udo.edu> wrote:
>
>> Arnaud HERITIER wrote:
>>
>> =A0I think there's no value to block all releases, waiting for this fix.=
I
>>> agree, support this change, but it won't help our users to have them
>>> waiting
>>> all our releases for several weeks.
>>>
>>
>> I don't really understand why fixing a project to produce a proper sourc=
e
>> bundle (e.g. by means of copying one of the existing assembly descriptor=
s)
>> would take several weeks...
>>
>
> It should take a few minutes and can be done with the current assembly
> release. The changes i made to the plugin are to make it possible to set
> this up at a top level pom (maven or asf) and have it do the right thing =
for
> each build.

The problem is that neither myself or Arnaud have a lot of capacity to
cut another release.

If I can get an explicit and complete set of instructions to build
whatever is required then I can do it.
If I have to spend any time thinking about it or start the release
process again then it will have to wait until I have spare time.

My preference is to:
* update the pom on trunk to include whatever will build the source
distro (this is different than the "-sources.jar") [Note: I dont
really want to change my pom I want the parent pom release profile to
do it for me instead]
* run the command to generate the distro archive from the tag
* deploy the distro

Suggestions?

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