Use version 0.13. Update build.sbt to cross compile.

[danhper]

Change xsbt-gpg plugin to sbt-pgp plugin as the former is not available with the current version of sbt.

Update build.sbt to update Scala 2.9 patch version and to cross compile with versions 2.9.2 and 2.10.3.

I did not found any incompatibility so the project should cross compile properly. The cross build and artifact publish should work with

sbt +compile
sbt +publish

[velvia]

@tuvistavie many thanks. I wonder if we shouldn't just upgrade wholesale to 2.10, after all 2.11 is almost out.

Would you mind updating the README as well so that folks know how to publish for 2.10?

[danhper]

@velvia Thanks for the answer. I also think that there is not really any need to keep the 2.9 compatibility further. Would you like me to add a commit to remove the 2.9 build?

Would you mind updating the README as well so that folks know how to publish for 2.10?

To fetch the dependency, what is currently in the README

libraryDependencies += "com.github.velvia" %% "scala-storm" % "0.2.2"

should work just fine with either version 2.9 or 2.10.

By publish, do you mean publishing to Sonatype? I am not really sure how it would be possible without the proper authorizations though.

In the meanwhile, as I wanted to start using it for one of my projects, I published the updated version to my personal repository, so feel free to give it a try before merging if you wish to. It should build without any problem with sbt 0.13 and the following settings.

scalaVersion := "2.10.3"

libraryDependencies ++= Seq(
  "storm" % "storm" % "0.9.0.1" % "provided" exclude("junit", "junit"),
  "com.github.velvia" %% "scala-storm" % "0.2.3-SNAPSHOT",
  "net.debasishg" %% "redisclient" % "2.12"
)

resolvers ++= Seq(
  "clojars" at "http://clojars.org/repo/",
  "clojure-releases" at "http://build.clojure.org/releases",
  "tuvistavie" at "http://repo.tuvistavie.com/content/groups/public"
)

[pkallos]

:+1:

[velvia]

@tuvistavie Go ahead and remove Scala 2.9 from the build. I'll follow up by testing against Storm 0.9.0.1 or thereabouts and republish. Thanks!

(Actually I'm tempted to publish to Bintray, which is far far easier. They have some kind of integration with Maven central.)