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

Pants

Where we pass `-m cProfile` and the path to the output if `PANTS_PROFILE` exists

Basically copy the way it's done in pantsbuild

And then that script will do all of the legwork of making graphs and such

```    register('--jvm-options', advanced=True, type=list_option, default=[],
             help='Run the compiler with these JVM options.')```

`fs` is just a weird wrapper, and I'd prefer to not have to use `fs` to get this functionality

huh, I thought jvm-options was fingerprint=True

True, I'm annoyed that neither calls the other.

<@U098KD4HJ>: based on the discussion above on <http://github.com/pantsbuild/pants/issues#issue/2049>, I think we can just drop the issue. Are you looking for other starter issues to work on? I’ll be happy to help you find something else.

Sweet :simple_smile: Yes, I’d love another issue to work on!

<@U053HNE90>, <@U051221NF> : to be clear, `./pants` is also a weird wrapper

Hey <@U06A03HV1> how within a compiler plugin would we get a handle on what the classfile output directory is?

Is there an API to just "output a file" like a classfile or in this case a resource?

Like an annotation processor must figure this out somehow

scalac... probably does as well somewheres

I noticed that ./pants paths only prints paths with -ldebug on and it has no tests and it uses the wrong idiom for a ConsoleTask subclass. I’m looking at cleaning that up

<@U053HNE90>: the closest i've gotten to scalac plugins is sbt's own plugins, which it uses for the dependency tracking

The oooold pants scalac plugin for tracking: <https://github.com/twitter/commons/blob/2a6aced7ce94dd5d269ac026405837ace1c87970/src/scala/com/twitter/common/tools/compiler/plugins/DependencyEmitter.scala>

<@U098KD4HJ>: Do you mind working in our java code?  Or do you want to stick with Python only?