commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell" <flame...@gmail.com>
Subject Re: [VOTE] Release Validator 1.3.0 based on RC2
Date Sat, 18 Mar 2006 05:30:11 GMT
On 3/17/06, Rahul Akolkar <rahul.akolkar@gmail.com> wrote:
> On 3/17/06, Niall Pemberton <niall.pemberton@blueyonder.co.uk> wrote:
> > I have just uploaded release candidate 2 (RC2) for Commons Validator 1.3.0.
> > The main differences from RC1 was to remove further references to the
> > cancelled 1.2.1 version..
> >
> <snip/>
>
> Source tarball builds / sites.

Yep. Builds (lots of error noise, but trunk makes the same noise).

Dist builds. Various errors on the way (jsdoc fails, svn fails) but it
suceeds as a job-wise (takes forever :) [8 minutes] ).

> Couple of comments:
>  * md5s do not verify.
>  * no sigs available to verify.
>
> Can someone please confirm / refute my md5 observations?

Confirmed:

ERROR: Checksum stored in commons-validator-1.3.0-RC2-src.zip.md5 does
not match commons-validator-1.3.0-RC2-src.zip
Correct hash:  945b7f27b34006259405a086587b8de5
File contents: 99b24844a16e59734a06dd2fa0d11c30

All of the md5 files have the same contents - so definitely a problem there.

Need sigs - and pointer to the KEYS file to use them with.

Should we be worried that the trunk of validator failed its gump
build? Works fine for me locally using Maven, but the Ant one requires
setting up N variables and after years of Maven I just hate having to
do that.

Hen

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


Mime
View raw message