This turned out to be because I was inadvertently using maven 2.2 for
these releases, which has a problem with uploading files twice to
nexus, and calculating the checksum on the doubled file.
John Casey regenerated the checksums on all the staging repos for me.
I checked a couple and they match my local checksums. Do you have a
moderately automated way to check these or should I go through and
verify them all one by one?
I'm hoping that since the actual artfifacts didn't change, just the
derived checksums, we won't need to reroll the staging and vote. WDYT?
thanks
david jencks
On Sep 14, 2009, at 11:56 AM, Kevan Miller wrote:
Dave,
It looks like the md5 and sha1 checksums are bad on all of your
release votes. I'm now -1 until resolved.
--kevan
On Sep 10, 2009, at 10:08 PM, David Jencks wrote:
It's time for the first release of our jaspic implementation for
inclusion in g. 2.2.
Release artifacts staged here:
https://repository.apache.org/content/repositories/geronimo-staging-003/
Site staged here:
http://people.apache.org/~djencks/staging-site/maven/components/geronimo-jaspi/1.0/
When used in geronimo with tomcat or jetty, this passed the jaspic
tck web profile. So far we don't try to implement the soap profile
in geornimo; this implementation should support both.
[ ] +1 release this
[ ] 0 dunno
[ ] -1 don't release this.
Vote open for 72 hours.
thanks
david jencks
