A plugin for sbt-0.(12|13).x that transforms *.proto files into gazillion-loc Java source files, and potentially to other languages too.

In your project, create a file for plugin library dependencies project/build.sbt and add the following lines:

addSbtPlugin("com.github.gseitz" % "sbt-protobuf" % "0.3.3")

The dependency to "com.google.protobuf" % "protobuf-java" is automatically added to the Compile scope. The version for protobuf-java can be controlled by the setting version in protobufConfig (set to 2.5.0 by default).

To actually "activate" the plugin, its settings need to be included in the build.

import sbtprotobuf.{ProtobufPlugin=>PB}

seq(PB.protobufSettings: _*)

import sbt._

import sbtprotobuf.{ProtobufPlugin=>PB}

object MyBuild extends Build {
  lazy val myproject = MyProject(
    id = "myproject",
    base = file("."),
    settings = Defaults.defaultSettings ++ PB.protobufSettings ++ Seq(
        /* custom settings here */
    )
  )
}

Assuming an artifact contains both *.proto files as well as the binaries of the generated *.java files, you can specify the dependency like so:

libraryDependencies += "some.groupID" % "some.artifactID" % "1.0" % PB.protobufConfig.name // #1

libraryDependencies += "some.groupID" % "some.artifactID" % "1.0" // #2

Line #1 tells sbt-protobuf that the specified artifact contains *.proto files which it needs to extract and add to the --proto_path for protoc. Internally the setting externalIncludePath is used to track 3rd party proto files.

Line #2 adds the artifact to the regular compile classpath.

The *.proto files of dependencies are extracted and added to the --proto_path parameter for protoc, but are not compiled.

Sometimes it's desirable to compile external proto files (eg. because the library is compiled with an older version of protoc). This can be achieved by adding the following setting:

sourceDirectories in PB.protobufConfig <+= (externalIncludePath in PB.protobufConfig).identity

*.proto files can be included in the jar file by adding the following setting to your build definition:

unmanagedResourceDirectories in Compile <+= (sourceDirectory in PB.protobufConfig).identity,

By default, the compiled proto files are created in <project-dir>/target/<scala-version>/src_managed/main/compiled_protobuf. Changing the location to <project-dir>/src/generated can be done by adding the following setting to your build definition:

javaSource in PB.protobufConfig <<= (sourceDirectory in Compile)(_ / "generated")

WARNING: The content of this directory is removed by the clean task. Don't set it to a directory containing files you hold dear to your heart.

All options passed to protoc are configured via the protobuf-protoc-options. To add options, for example to run a custom plugin, add them to this setting key. For example:

protocOptions in PB.protobufConfig :+= Seq("--custom-option")

The source directories where the files are generated, and the globs used to identify the generated files, are configured by generatedTargets in PB.protobufConfig. In case only Java files are generated, this setting doesn't need to change, since it automatically inherits the value of javaSource in PB.protobufConfig, paired with the glob *.java. In case other types of source files are generated, for example by using a custom plugin (see previous section), the corresponding target directories and source file globs must be configured by adding them to this setting. For example:

generatedTargets in PB.protobufConfig <++= (sourceDirectory in Compile){ dir =>
    Seq((dir / "generated" / "scala", "*.scala"))
}

This plugin uses the generatedTargets setting to:

• add the generated source directories to cleanFiles and managedSourceDirectories
• collect the generated files after running protoc and return them to SBT for the compilation phase

All settings and tasks are in the protobuf scope. If you want to execute the protobuf-generate task directly, just run protobuf:protobuf-generate.

sbt-protobuf is based on softprops/coffeescripted-sbt for the sbt-0.10 specific parts and codahale/protobuf-sbt for the protobuf specifics.