regarding pants

Currently, we have Pants as the primary build tool, but we still have pom.xml files and we still auto-generate BUILD files from them. This quarter, Garrett and I are focusing on getting us out of the auto-genration business. That's why I'm working on this parallel testing feature (we still have a small CI that runs maven to run some tests.) We've been planning since last year for primary responsibilities to be moved to a team in San Francisco once we successfully remove all remnants of maven from the build. @brash-oxygen-26029 (Chris Heisterkamp) is on that team.

Actually, I should have said that that was our focus last quarter, we were supposed to be done by now 😞

Hey, I am looking for a way to add the

-Xmax-classfile-name=75

option to scalac, is there a place in pants.ini where this can be configured?

Here's an example from Foursquare's OSS pants.ini: https://github.com/foursquare/fsqio/blob/master/pants.ini#L170

Not of that particular option, but how to set JVM options for zinc compilation

Oh actually

You'll probably need

args

rather than options, since you're plumbing all the way down into scalac

e.g. https://github.com/foursquare/fsqio/blob/master/pants.ini#L196

The

-S-

tells zinc to thread that option down into scalac

hmm yeah, this works for scala when using

-C-

but then java dependencies fails on the unknown option

and it does not work when doing

-S-

do you have any idea how to block it from being passed to javac, or is that exactly what

-S-

is supposed to do?

Think to thread to javac from zinc, you need to do

-S-C-

ah figured it out, the arg I needed have to be split in 2 like this:

'-S-Xmax-classfile-name',
    '-S75'

thanks for the help

Ah yeah, sorry. The args are threaded individually

np

Also to give a bit of post context, this was a fix for using an encrypted home folder that ended up giving an IOException filename too long when compiling scala

Above @mysterious-action-44812 had questions about testing out pants in other repos. Here is the 3-part recipe:

PANTS_PYTHONPATH="['/home/jsirois/dev/pantsbuild/jsirois-pants/contrib/python/src/python']" \
PANTS_PLUGINS="[]" \
PANTS_BACKEND_PACKAGES="['pants.contrib.python.checks']" \
/home/jsirois/dev/pantsbuild/jsirois-pants/pants -ldebug --print-exception-stacktrace test src/main/python:: src/test/python:: -- -v

This is me working https://github.com/pantsbuild/pants/issues/3188 in the aurora repo using pants from the pants repo

Plugins always forced empty and each plugin gets an entry in the other 2 env var lists

Sorry-- @witty-crayon-22786 re intransitive tasks

It seems like, despite double checking all of the code that produces cache keys correctly being intransitive, it's still invalidating based on upstream changes

should just be based on your

invalidate_transitive=True

parameter to the invalidated block

Yeah, that's false (also the default)

slash False

And this is just a vanilla task

would add some debug code in there then... don't know why that wouldn't be working.

Oh you know what

I know what's going on