Skip to content
Scala Java Shell
Latest commit fc5a094 May 10, 2013 @penberg penberg Merge pull request #25 from chrisdinn/raise-error-on-connection-failure
Throw exception if either bind or connect fails.
Failed to load latest commit information.
src Throw exception if either bind or connect fails. May 8, 2013
.gitignore zeromq-scala-binding: Add 'tags' to .gitignore Sep 30, 2011
LICENSE zeromq-scala-binding: Add LICENSE May 7, 2012
README.md Update README Dec 10, 2012
TODO zeromq-scala-binding: Add version checks to JZMQ like API Nov 15, 2011
build.sbt
sbt zeromq-scala-bindings: Add build based on simple-build-tool 0.11 Sep 29, 2011
sbt-launch.jar Upgrade to SBT 0.12.0 Oct 3, 2012

README.md

Scala Binding for ZeroMQ

The Scala binding for ZeroMQ is based on ZeroMQ versions 2.1.x and uses JNA for accessing native functions. It is a thin wrapper of the ZeroMQ API, but offers also a jzmq-like API intending to be compatible with the Java binding for ZeroMQ; users of the Java binding wanting to access ZeroMQ over JNA can switch over to the Scala binding.

Installation

Scala binding for ZeroMQ is made available through a Maven repository. If you're using SBT, ament your build.sbt with:

resolvers += "Sonatype (releases)" at "https://oss.sonatype.org/content/repositories/releases/"

libraryDependencies += "org.zeromq" %% "zeromq-scala-binding" % "0.0.9"

Configure for GPG signed artefacts

When publishing a package to OSS Sonatype, you may sign the artefacts by adding the following lines to project/plugins.sbt:

resolvers += Resolver.url("sbt-plugin-release", new URL("http://scalasbt.artifactoryonline.com/scalasbt/sbt-plugin-releases")) (Resolver.ivyStylePatterns)

addSbtPlugin("com.typesafe.sbt" % "sbt-pgp" % "0.7")

Also, you need create a file containing your Sonatype credentials ~/.sbt/sonatype.sbt:

credentials += Credentials("Sonatype Nexus Repository Manager",
                           "oss.sonatype.org",
                           "your-sonatype-username",
                           "your-sonatype-password")
Something went wrong with that request. Please try again.