On 07/07/2008, at 11:32 PM, Jason van Zyl wrote:
But is that hiding another bug? We are wiping out the artifacts
once a day on Hudson, but everyone seems to be able to run them
locally. So now we're just nuking everything but is that just
hiding a dependency resolution bug? I hate just diddling the ITs
and then stuff starts working.
With regard to the issues you had on Hudson? No, it was a straight
up fix in maven-artifact where it tried to calculate the checksum
of a checksum unnecessarily, which I fixed.
And this didn't show up for anyone else except Hudson why? We were
only nuking the repo once daily.
It's because there's no sha1 here:
http://repo1.maven.org/maven2/commons-io/commons-io/1.4/
It wasn't showing in Continuum because it hadn't been building the
latest versions of maven-artifact that introduced the bug in an
attempt to fix another variation of it. It is now.
I suggest if you review the commit I made (particularly the unit
test), it will make it quite apparent what was going on.
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
