sbt-protobuf

A plugin for sbt that transforms *.proto files into gazillion-loc Java source files, and potentially to other languages too.

Usage

Adding the plugin dependency

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

addSbtPlugin("com.github.sbt" % "sbt-protobuf" % "0.7.1")

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 ProtobufConfig / version (set to 3.9.0 by default).

Importing sbt-protobuf settings

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

build.sbt

enablePlugins(ProtobufPlugin)

Declaring dependencies

Artifacts containing both *.proto files and java binaries

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" % 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 protobufExternalIncludePath 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.

Artifacts in the protobuf configuration containing only *.proto files

You can specify a dependency on an artifact that contains only .proto files in the protobuf configuration with a proto classifier like so:

libraryDependencies += ("some.groupID" % "some.artifactID" % "1.0" classifier protoClassifier) % s"${ProtobufConfig.name}->${ProtobufConfig.name}"

Compiling external proto files

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:

ProtobufConfig / sourceDirectories += (ProtobufConfig / protobufExternalIncludePath).value

Packaging proto files

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

Compile / unmanagedResourceDirectories += (ProtobufConfig / sourceDirectory).value

Alternatively, *.proto files can be packaged in a separate jar file in the protobuf configuration with a proto classifier:

addArtifact(ProtobufConfig / protobufPackage / artifact, ProtobufConfig / protobufPackage)

Changing the location of the generated java files

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:

ProtobufConfig / javaSource := ((Compile / sourceDirectory).value / "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.

Note

1. If you encounter compile errors, as [...] is already defined as object [...] you could change the compile order as compileOrder := CompileOrder.JavaThenScala,the default is mixed.

2. The inner message's name could not be the .proto's file name.that will cause problem too, you could change the inner message's name or the .proto file name or add the option java_outer_classname = "NewNameNotAsTheFileName"; to you .proto file.

Additional options to protoc

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

ProtobufConfig / protobufProtocOptions ++= Seq("--custom-option")

Additional target directories

The source directories where the files are generated, and the globs used to identify the generated files, are configured by ProtobufConfig / protobufGeneratedTargets. In case only Java files are generated, this setting doesn't need to change, since it automatically inherits the value of ProtobufConfig / javaSource, 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:

ProtobufConfig / protobufGeneratedTargets ++= {
  Seq(((Compile / sourceDirectory).value / "generated" / "scala", "*.scala"))
}

This plugin uses the protobufGeneratedTargets 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

Scope

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

Settings

Tasks

IntelliJ IDEA BSP bug

IntelliJ has a bug where it only recognizes generated sources if there is at least one Scala class in the same package - otherwise you'll see red squiggles. As a workaround, you can configure your project to add a private empty class, e.g. like this:

Compile / sourceGenerators += Def.task {
  // adapt this for your build:
  val protoPackage = "org.example.proto.foo"

  val scalaFile = (Compile/sourceManaged).value / "_ONLY_FOR_INTELLIJ.scala"
  
  IO.write(scalaFile,
    s"""package $protoPackage
      |
      |private class _ONLY_FOR_INTELLIJ
      |""".stripMargin)

  Seq(scalaFile)
}.taskValue

Credits

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