HHi,
This could cause wrong checsums:
Quote from Kevan: "Maven 2.2 was used in creating the xbean 3.6 release.
Evidently 2.2 had an issue uploading files to Nexus twice and
calculating checksums on the doubled files."
http://old.nabble.com/Maven-central-has-corrupted-artifact-org.apache.xbean%3Axbean-finder-shaded%3Ajar%3A3.6-ts27340027.html#a27340027
rgds,
Markku
On 21.4.2010 10:14, Milos Kleint wrote:
On Wed, Apr 21, 2010 at 8:41 AM, Brett Porter<br...@apache.org> wrote:
On 21/04/2010, at 3:40 PM, Milos Kleint wrote:
hmm... I did the plexus compiler release indeed. No idea how the
checksums
became broken. I've done the regular release:prepare, release:perform
combo.
I can't recall any problems with the process. I specifically double
checked
that there are gpg signatures, but assumed checksums are correct. They
never
been broken for me before.
Did you use Maven 2.1.0, Maven 2.2.0, or the httpclient wagon perhaps?
Not sure, I would say 2.2.x. I don't have the computer anymore where I did
the release.
What do we do now?
If the signatures are intact, then we can say the artifacts are and you
could upload corrected checksums. Let me know if you need any help.
gpg --verify plexus-compiler-javac-1.8.jar.asc
gpg --verify plexus-compiler-javac-1.8.pom.asc
both say
gpg: Signature made Tue Mar 30 00:28:04 2010 CEST using RSA key ID B0874707
gpg: Good signature from "Milos Kleint<mkle...@apache.org>"
How do I recreate and reupload the correct checksums?
thanks.
Milos
- Brett
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
