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

Pants

(with the isolated strategy, they're actual compile failures)

Yep, we currently use `missing_deps=fatal`, but I think we would switch to isolated if we enable shared cache

the increased compilation time would we offset by the fact that the CI’s would have generally built every revision

<@U053J9JB4>: do you see increased compilation time as it stands?

what if I’m not using zinc?  (I think by default it uses jmake, right?)

you won't get good incremental behaviour with jmake+isolation

actually, did the default value for this change recently?

--compile-java-strategy=&lt;str&gt; (default: isolated # Enabling this exposes lots of compilation warnings.)
    Selects the compilation strategy to use. The "global" strategy uses a shared
    global classpath for all compiled classes, and the "isolated" strategy uses
    per-target classpaths.

the defaults are overridden by your pants.ini though

oh… I see.  The ‘default’ value in the help is already modified by the pants.ini

well <@U06A03HV1> I’ll put trying out zinc for java compilation on the list of things to do.  I’m basically the ‘manage the pants build’ guy here, so I’m happy to coerce our build into whatever is easiest to support.  If ‘zinc for java’ is recommended, I’ll definitely give that a whirl.  Additionally, I’m interested in the consensus on what the preferred thrift generation strategy is.

i.e. is scrooge generally the future, or only the future for finagle users?

for us for finagle. but it needs work (not isolated, not cached)

oh boy, I’ve never even heard of that one

Keep in mind - none of those handle the languages apache thrift does - today - IIUC

You could write a python backend for scrooge though

Or just continue to use apache for python

well that I don’t really mind, because we don’t really need finagle support for python