Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Hey, we would like to add support for another scala test framework (zio), should we do it separately as plugin or as part of pants?

Ohhh my passive understanding is Zio has tons of traction, so I think this could be really useful? Thoughts?

Maybe a target like `zio_tests` or `scala_zio_tests`?

And probably a dedicated backend like `pants.backend.scala.test.zio` to activate it? We bias towards making things opt-in so that there is less noise, e.g. `./pants help targets` is less crowded

cool, I'm working on something at the moment as plugin in our code base, will turn into plugin after.

It is based on running the main function in the test file, without actually dependency on a runner.
I'm using the scala parser to find the name of the main class.