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

Pants

I think the bootstrap is, 1) download a known ivy jar, 2) download workspace specified ivy version using jar from 1

curl the jar, then re-resolve a more complete ivy cp if needed

oh so the problem for me (i think) is that i cannot specify java options for that command above

which i *think* i need to do to use a custom ssl.keyStore

we support setting up proxies, but that's about it iirc for the phase2

is there anything that should prevent us from having `tests/unit` and `tests/integration` as test roots?

a team member tried that out and had problem with the intellij plugin -- intellij was always asking this:

Pasted image at 2016_03_07 05_40 PM.png

<@U0NULBW4B>: something related _may_ have changed in master recently

<https://rbcommons.com/s/twitter/r/3522/>

<@U0EH3DM7W>: that should work. i expect that the patterns weren't configured correctly

<@U0EH3DM7W>: but note that the pantsbuild/pants repo has switched to using tags for that usecase

for example, `./pants --tag='-integration' test tests/python/pants_test/engine/exp/::` runs in 10 seconds

`./pants --tag='+integration' test tests/python/pants_test/engine/exp/::` runs in 60 seconds

and  `./pants test tests/python/pants_test/engine/exp/::` runs in about 70

I'm going to proceed with the release in ~15 minutes if there is no further feedback on the CHANGELOG rb: <https://rbcommons.com/s/twitter/r/3542/>

Thanks.
Alrighty, release is away <https://pypi.python.org/pypi/pantsbuild.pants/0.0.75>

how do most people have ivy set up to resolve conflicts?

<@U0NULBW4B>: we use the default conflict resolution in ivy (most recent version by some kind of sorting of the artifact version), but are using `managed_dependencies()` to try to pin as much as possible.