Results 1 to 2 of 2

Thread: Spring Blazeds-Integration 1.5.0.M1 SHA1 is messed up

  1. #1
    Join Date
    Aug 2005
    Location
    Milton Keynes, UK
    Posts
    39

    Default Spring Blazeds-Integration 1.5.0.M1 SHA1 is messed up

    http://s3.amazonaws.com/dist.springf...-dist.zip.sha1

    Result reads:
    NoSuchKeyThe specified key does not exist.milestone/FLEX/spring-flex-1.5.0.M1-dist.zip.sha10E4347AC5173E200KDH6Yv//I0Las0Tkqs3o0awze/2mdnD2fseETyzMpteW8uxVlvUH1vEHIbnVMHBe

    Can someone confirm the correct value?

  2. #2
    Join Date
    Apr 2005
    Location
    San Francisco, CA
    Posts
    1,224

    Default

    I don't believe we ever actually uploaded a SHA1, as we had to do things manually with the last release. The system that aggregates the links from S3 just assumes that one is there, which is why there is a link that doesn't actually work.
    Jeremy Grelle

    Staff Engineer, Web Products Team
    SpringSource

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •