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

Pants

Hi! Do we have an example of pants2 and pants1 setup side by side?

it looks like we had a page until version `2.4.x` : <https://www.pantsbuild.org/v2.4/docs/how-to-upgrade-pants-2-0>

i don’t actually know which version of 2.x i would recommend targeting.

but most likely the general advice to “validate but not necessarily ship” each minor version of pants (to get deprecations) probably applies (<https://www.pantsbuild.org/docs/upgrade-tips>)

sure thing: let me know if you have other questions!

The main thing would probably be to tell pants2 to use a `pants2.toml`  as its config (via env var, or flag), and then in that config tell pants2 to use BUILD2, say, as the buildfile name

then you avoid collisions on config and metadata