Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <f2e8eedf0802192032x3a71f5cnfd8a7d61dedaf6a8@mail.gmail.com>
Date: Tue, 19 Feb 2008 23:32:09 -0500
From: "James Carman" <james@carmanconsulting.com>
Sender: jcarman@carmanconsulting.com
To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Subject: Re: [VOTE] Release Proxy 1.0 (from rc2)
In-Reply-To: <f2e8eedf0802192025i3ee632d0m7452f7b7b416fa27@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <f2e8eedf0802191531h69e8febfje4e727ede313edd4@mail.gmail.com>
	 <55afdc850802191948v72831f57lf86cfc38686d7df1@mail.gmail.com>
	 <f2e8eedf0802192025i3ee632d0m7452f7b7b416fa27@mail.gmail.com>

On 2/19/08, James Carman <james@carmanconsulting.com> wrote:
> On 2/19/08, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> > I'm +0 on this release because I like to review the actual artifacts
> > that are going to be distributed. The distros IMO meet ASF release
> > requirements but if I run command "mvn -Prc site assembly:assembly"
> > then the binary distro created also includes the javadocs and also
> > -sources.jar and -javadoc.jar. Which kind of makes the argument for
> > reviewing actual artifacts.
>
> Is there something in the pom that shouldn't be there?  I don't think
> there's anything too crazy in the pom that should cause it to be
> generating weird artifacts.  Is it something in the parent pom?

Are we supposed to be using the "rc" (I take it that means release
candidate) profile when building?  That wasn't in the instructions.
The distros that I built were done using mvn assembly:assembly and
site without the profile activated.  Then, I hand-signed the artifacts
and generated the md5 checksums.  I guess I could have used the maven
plugin, huh?  :)

>
> >
> > Niall
> >
> > On Feb 19, 2008 11:31 PM, James Carman <james@carmanconsulting.com> wrote:
> > > All,
> > >
> > > I have prepared a commons-proxy-1.0-rc2 release candidate.  The
> > > distribution files can be found at:
> > >
> > > http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> > >
> > > and the site can be found at:
> > >
> > > http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> > >
> > > The SVN tag used to create the release can be found at:
> > >
> > > http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> > >
> > > All issues brought up thus far with the first release candidate have
> > > been addressed.  Again, this is my first release (including signing),
> > > so please review thoroughly (not that you normally don't).
> > >
> > > Thank you,
> > >
> > > James Carman
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>

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