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

Pants

<http://pantsbuild.github.io/setup_repo.html>

this is an existing repo with a functioning installation

and actually the pants wrapper generated by <https://github.com/pantsbuild/setup/blob/gh-pages/pants.sh> works great

...jeez, `junit_run.py` is such a shitshow.

need to take a survey of which features people actually use and kill everything else.

<@U083H6LRL>: <https://github.com/pantsbuild/setup/issues/1>

yes, junit_run.py needs to be rewritten from scratch, frankly.

Micro-optimizing that code, or even adding caching, would not be fun

<@U051221NF>: any objections to getting <https://rbcommons.com/s/twitter/r/2561/> in?

Thank you sir. Will wait for the last set of notes and then merge.

<@U053HHEDG>: good morning sir. would you mind taking a look at <https://rbcommons.com/s/twitter/r/2576/> ?

is there a release tomorrow and will this change go with it? <https://rbcommons.com/s/twitter/r/2567/>

We missed a debug check in the jvm subsystem changes <https://github.com/pantsbuild/pants/issues/1931>

also, I think BenchmarkRun may be missing a test suiet

i can't seem to think of a reasonable workaround for this other than manually blowing away the chroot on every change, any ideas? <https://rbcommons.com/s/twitter/r/2567/>

yeah, our users are just doing a clean-all to eliminate the chroots if/when this is encountered

<@U071M9KNE>: thanks for diving into the ivy classifier stuff with <https://rbcommons.com/s/twitter/r/2579/>   I don’t really see any  major problems with it, but I wanted to ask you if the export format is changing at all, or are you intentionally keeping it the same.  There was the one part where you create a key for the jar to look it up in another table where I would like to add in ‘classifier’ (and later type), but I’m afraid that would cause an incompatibility.