LCartwright is correct that this is due to the SHA-1 hash file differring from the hash of the POM on maven central.
To get around this you can add the JBoss maven repository, where the hash matches, to your resolvers in the global sbt config ~/.sbt/0.13/global.sbt
resolvers += "JBoss" at "https://repository.jboss.org/"