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

Pants

Yeah, most of them. Wire we need because we use a different version of it and include extra deps on its classpath.

<@U04S45AHA>: Easy enough to add the error message to `    def dep_spec(self, options):` in `jvm_tool_mixin.py`, but not sure how to check to see if the spec is missing elsewhere with the `is_default` logic. In the debugger it looks like `self.context.resolve("':fake-wire-compiler'")` resolves to a synthetic `JarLibrary` object which holds the default classpath. I’m not sure where that synthetic target is generated.

BootstrapJvmTools._alternate_target_roots

thats where all this new checking code goes

<https://github.com/pantsbuild/pants/blob/master/src/python/pants/backend/jvm/tasks/bootstrap_jvm_tools.py#L107-L142>

The bug today is in handling the AddressLookupError

The handling assumes - just use the default classpath if one is defined

How do I test pass thru args on a console task? I was using ConsoleTaskTestBase.assert_console_output() previously, but it doesn’t appear to handle pass thru args.

So, all test code funnels down through BaseTest to here: <https://github.com/jsirois/pants/blob/master/tests/python/pants_test/option/util/fakes.py#L82-82>

That has no plumbing for passthru args, it just always returns []

So you'll need to start by plumbing passthrough, maybe change the signature to `create_options(options, passthru_args=None)`

then in the fake return `passthru_args or []` instead of the current `[]`

Once you have that you should be able to work backwards to BaseTest and add a complement to `set_options`, maybe `set_passthrough_args`

And then finally use that in your stuff / the ConsoleTaskTestBase

<@U04S45AHA>: posted <https://github.com/pantsbuild/pants/pull/2168/files>

we arent putting Pants’ bootstrapped node on PATH unfortunately

and that will cause lots of node modules to fail

OK - that can be fixed, for example, in `NodeTask.execute_npm`.  That can pass an ephemeral patched up env to the npm subprocess.

I won't review the PR, I'll hang back until an RB gets posted

Has anybody worked with a docker image for dev that mounts host dirs and dealt with the perm issues?

Could I get some comments on <https://github.com/pantsbuild/pants/issues/2173>?

I'm dumb here - how does the incremental compile work - it clearly doesn't nuke dead classfiles - so it there any artifact that can signal pants what the dead ones are?