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

Pants

<@U04S45AHA> Ha...its from a British comic book called Judge Dredd. At one point they put a pet fish in charge. 

[illuminati pants (kwlzn/psutil_upgrade)]$ find . -name CHANGELOG
[illuminati pants (kwlzn/psutil_upgrade)]$

am I missing something obvious re: how to update the CHANGELOG?

So, <@U06A03HV1> released pants 0.0.39 into Twitter last night (yay!)

However, I'm having a bit of trouble groking the new options (which look much nicer tho)

Previously, we could do something like `./pants test &lt;target&gt; --test-junit-debug`

But I'm a bit stumped as to what the new equivalent is

```[prometheus source2 (areitz/re-add_publish_validation)]$ ./pants test -h --help-advanced|grep debug
--[no-]jvm-test-junit-debug (default: None)
    Run the JVM with remote debugging.```

But I don't see anything in the general help. I hear that `--jvm-debug` works

but not sure how to tell folks to fish for that answer

I started looking at <https://github.com/pantsbuild/pants/issues/1489> and wonder which path to choose. Just change a format of export goal output or change IvyModuleRef to include classifier as <@U053H6LQS> suggested.

Changing IvyModuleRef will be backward compatible with the plugin for example.

<@U06A02Y4T>: You need to fully qualify the task in this case

I'm looking at this <https://rbcommons.com/s/twitter/r/2466/diff/1#index_header>

it seems like there is a way for options to go up to the jvm level

but I'm confused about how to see this in the help

I don't want to tell users to use `--help-advanced` -- that's for admins, IMO

and we've been doing pretty good having folks look in the help for options that they need

<@U06A02Y4T>: —jvm-debug discussed before in <https://groups.google.com/forum/#!topic/pants-devel/fPyKDLnGOKI>    Essentially, the subsystem help still needs to be completed and its slated for a couple of weeks