#373
  • Created on
    2010-08-06 16:57
  • Reported by
    bruce.mitchener
  • Status
    Invalid
  • Priority
    Low (4)
  • Assigned to
    viktorklang
  • Milestone
    1.0-MILESTONE1
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

SHA1 hashes missing for POM and JAR files

Not seeing SHA1 hashes of the POM and JAR files when doing a build. This causes warnings from Maven when we deploy them to our internal Maven repository. It'd be nice if the build process autogenerated those.
User picture
  on 2010-08-09 10:19 *
By Jonas Bonér
Milestone set to 0.11
User picture
  on 2010-08-19 19:08 *
By Jonas Bonér
Milestone changed from 0.11 to 1.0
Updating tickets (#135, #181, #194, #207, #208, #209, #228, #230, #231, #250, #255, #257, #258, #259, #261, #262, #263, #264, #265, #273, #298, #299, #300, #322, #323, #326, #343, #346, #363, #364, #373, #378, #380, #381, #384, #385, #387, #399)

Skipping 0.11. Next release is 1.0.
User picture
  on 2010-09-02 14:36 *
By Jonas Bonér
Is this an SBT problem?
User picture
  on 2010-09-02 14:37 *
By Jonas Bonér
Priority changed from Normal (3) to Low (4)
User picture
  on 2010-09-16 15:35 *
By viktorklang
Assigned to set to viktorklang
Status changed from New to Accepted
User picture
  on 2010-09-17 09:23 *
By viktorklang
Status changed from Accepted to Invalid
Should be fixed in SBT,
Future releases of Akka should be published in the public repo with associated .sha1 files, this means using http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html#createChecksum when doing mvn install-file