I'll edit the md5's by hand for now. Please file a JIRA for next time. FWIW, i really don't like the uncertainities involved with the maven deploy to production repo's. Haven't bothered to figure out how to do a staging repo :)
-- dims On Thu, Apr 24, 2008 at 10:11 AM, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > The md5 files on all the recent XmlSchema builds are corrupt in the maven > repo. (and there aren't sha1 files either) Same with the axiom stuff. > > Basically, they all have a leading "\" on them. Example: > \9d1ff1229a42b8a93fc1db8c349ce830 > > instead of just: > 9d1ff1229a42b8a93fc1db8c349ce830 > > Thus, maven is complaining. > > Now comes my question: how were these generated? Since those projects > are maven based, why wasn't maven just used to deploy and let maven > generate the md5/sha1 files? > > > -- > J. Daniel Kulp > Principal Engineer, IONA > [EMAIL PROTECTED] > http://www.dankulp.com/blog > -- Davanum Srinivas :: http://davanum.wordpress.com
