sbt 2 build

[mfirry]

Hi,

It looks like the configuration at:

https://github.com/typelevel/fs2-grpc/blob/update/sbt-2.0.0/.github/workflows/ci.yml#L32

needs to be updated for the update/sbt-2.0.0 branch to build successfully.

I noticed this from the failing GitHub Actions run:

https://github.com/typelevel/fs2-grpc/actions/runs/27648314105/job/81765765302#step:5:9

Unless I'm missing something, adjusting that workflow configuration should fix the build for this branch.

[ahjohannessen]

There a dependencies in project/plugins.sbt - Those need to be available for sbt2 before anything can be done.

[armanbilge]

To clarify: even though the fs2-grpc build needs the dependencies in plugins.sbt before it can be upgraded to sbt 2, the sbt-fs2-grpc plugin can be (cross-)published for sbt 2 without updating the build. (This is how Scala.js is publishing for sbt 2, for example).

fs2-grpc/build.sbt

Lines 80 to 112 in b338cff

	lazy val plugin = project
	.enablePlugins(BuildInfoPlugin, SbtPlugin)
	.settings(
	name := "sbt-fs2-grpc",
	scalaVersion := Scala212,
	tlVersionIntroduced := Map("2.12" -> "2.5.3"),
	mimaFailOnNoPrevious := false,
	mimaPreviousArtifacts := Set(),
	buildInfoPackage := "fs2.grpc.buildinfo",
	buildInfoKeys := Seq[BuildInfoKey](
	name,
	version,
	scalaVersion,
	sbtVersion,
	organization,
	"grpcVersion" -> versions.grpc,
	"codeGeneratorName" -> (codegen.jvm(Scala212) / name).value,
	"codeGeneratorFullName" -> codegenFullName,
	"runtimeName" -> (runtime.jvm(Scala212) / name).value
	),
	libraryDependencies += scalaPbCompiler,
	addSbtPlugin(sbtProtoc),
	scriptedBufferLog := false,
	scriptedLaunchOpts ++= Seq("-Xmx1024M", "-Dplugin.version=" + version.value),
	scriptedDependencies := scriptedDependencies
	.dependsOn(Def.taskDyn(runtime.jvm(Scala3) / publishLocal))
	.dependsOn(Def.taskDyn(codegen.jvm(Scala212) / publishLocal))
	.value,
	test := {
	(Test / test).value
	scripted.toTask("").value
	}
	)

[iRevive]

I believe we still need to get an sbt2-compatible release of sbt-protoc.
Once 1.1.0 is released, we can try to cross-publish the plugin.