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

Pants

<@U06A03HV1>: which goal currently will trigger `build_graph.inject_specs_closure`?

<@U0AALHEDR>: er... not in the new engine?

it's how commandline specs end up in the build graph

hmm that’s what i thought, sounds like my debugger is a bit funky

(unless it's been refactored i suppose...)

yeah, actually seeing any print statement within that function

<@U0AALHEDR>: <https://github.com/pantsbuild/pants/blob/master/src/python/pants/bin/goal_runner.py#L108-L126>

is `./pants run src/python/pants/engine/exp/examples:viz` moved to somewhere else?

```[tw-mbp-yic pants (master)]$ ./pants list :: | grep viz
tests/python/pants_test/engine/examples:viz
tests/python/pants_test/engine/examples:viz-fs```

yeah, now: `./pants run tests/python/pants_test/engine/examples:viz`

is junit:junit:4.12 supposed to show up under dependencies?

```[tw-mbp-yic pants (master)]$ ./pants dependencies testprojects/tests/java/org/pantsbuild/testproject/matcher:matcher
testprojects/tests/java/org/pantsbuild/testproject/matcher:matcher
3rdparty:junit
junit:junit:4.12```

its a dependency of that target, so why wouldn’t it?

```jar_library(name='junit',
            jars=[
              jar('junit', 'junit', '4.12')
            ])```

seems to me that the inner `jar` is indeed a target

<@U0AALHEDR>: 'dependencies' has special handling for 3rdparty

```$ ./pants help dependencies

dependencies options:
Print the target's dependencies.

--[no-]dependencies-external-only (default: False)
    Specifies that only external dependencies should be included in the graph
    output (only external jars).
--[no-]dependencies-internal-only (default: False)
    Specifies that only internal dependencies should be included in the graph
    output (no external jars).```