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

Pants

```
[jvm-platform]
default_platform: java6
platforms: {
    'java6': {'source': '6', 'target': '6', 'args': [] },
    'java7': {'source': '7', 'target': '7', 'args': [] },
    'java8': {'source': '8', 'target': '8', 'args': [] },
  }
```

What if I publish on a machine with only 8?

OK - so its just the config that is ... confusing as hell

```[jvm-distributions]
minimum_version: 1.8.0
maximum_version: 1.8.999```

I think this is exactly one of those things that warrants discussion not on slack

the decision to bump to 7? yea. but i can probably mail a link to the RB to pants-devel@ for discussion

OK - confirmed that the default platform doesn't mean what I think it means on a naive read - ie it does not work based on jdk, its only to set source and target

I think I knew this at one time, but find it confusing now on a blank slate read of the words

who knows a decent amount about annotation processors and can answer a question or two for me?

Namely, why we don’t use `-processorpath` and instead let javac find them on its regular classpath.

I assume -processorpath exists to avoid potential conflicts between annotation processors and user code?

So its probably there for legacy reasons at root; however you sould use it to do just code-gen rounds

Though I gues you can do that w/o processorpath, you can just use classpath

You are correct though, it could be the case a processor is on your classpath transitively and you don't want it to run but you do want your own direct deps processor to run

So the fact we don't control things like this today certainly causes someone somewhere troubles

<@U053HNE90>: is it enough to copy the 1 file in <https://github.com/pantsbuild/pants/pull/3276> , edit and push to github with 'CI this' to experiment on the new jenkins stuff independent of you?