needed*

For that you can use the mirror resolver and just have a checked in mirror file with the repo listed N times, but I'll demonstrate using ivy with the apache commons http client

@happy-kitchen-89482: to be clear, positional arguments to subsystems are not currently supported? so

./pants test.junit --jvm-options ...

will currently affect the global scope?

i'm considering blocking our next internal release on nailing all of this down

I actually want that to be supported, but it isn't yet.

I have a couple of pending changes that are steps on the road to this.

are you able to delegate any of them?

@witty-crayon-22786: I added a note to https://github.com/pantsbuild/pants/issues/1779 explaining retry enabling and its fully encapsulated by this commit: https://github.com/pantsbuild/issues-1779/commit/e8c25ab56f0c0c8ad8ee1cad1e866cf83953251b

we'd be happy to help with one or two

@happy-kitchen-89482: ^

@enough-analyst-54434: I am seeing a problem with the release procedure. http://pantsbuild.github.io/staging/zundel/howto_develop.html “Building a Pants PEX for Production”. It seems that although I have this requirements.txt:

-f /Users/zundel/Src/Pants/dist/
 pantsbuild.pants

the build of pants is pulling in pantsbuild.pants version 0.0.33 from pypi instead of my local directory.

nonmonophyletic is a very satisfying word

I take that back. I unziped the pex and it is the 0.0.34 release. What’s happening is that I am trying to add a patch on top of our stable branch which was built last week, so its still at version 0.0.33. my patch include a new flag, but my built pex doesn’t contain the flag. I looked at the .tgz in the pants dist/ directory created by pants_release.sh and it does have the updated flag. the

@fancy-queen-20734: that word choice by @kind-holiday-68516 learned me something new but sparked a long discussion with my wife about why oh why does english have a predilection towards gathering words like that! Just use the 3-5 other words!

thanks for the ivy retry explanation

*cough predilection

yw

@ancient-stone-50795: your last got cut off so I'm waiting on more - not sure if your question dissolved or is going to morph

No, my question isn’t dissolved. I just tacked an extra ‘the’ on the end. What’s happening in a nutshell is that i’m getting a ‘pants.pex’ in the second repo, but it is pulling in the latest pantsbuild.pants from pypi, not the version that

pants_release.sh

built in the pants source repo. I know this because my local pants repo has a custom patch in it that is not in the latest release.

@enough-analyst-54434: : its as if the

-f /Users/zundel/Src/Pants/dist/

at the top of the requirements file is being ignored.

2 things:

1. avoid the issue outright and if you're tweaking, tweak the version too, say 0.0.34-square

2. if you don;t want to do that, then it may be the repo needs to be listed in the pants.ini repos list ... looking at the plumbing now

But one is really the right answer it seems to me for general sanity sake

As long as your forked and not releasing from pants HEAD, it will be much easier to have confidence in pex builds when you can just

zipinfo pants.pex | grep "\-square"

to ensure your fork version is what got embedded

I’m giving it a whirl now.

@witty-crayon-22786: maybe? let me think about how to do this.

@enough-analyst-54434: I changed the version in the release.sh script to ‘square-201507-02’ and the release script fails in a similar way. Our dry run test is testing a non-local version I am afraid:

[== 00:50 Installing and testing package pantsbuild.pants-square-20150706-02 ... ==]

You are using pip version 6.1.1, however version 7.1.0 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
  Could not find a version that satisfies the requirement pantsbuild.pants==square-20150706-02 (from versions: 0.0.17, 0.0.18, 0.0.20, 0.0.21, 0.0.22, 0.0.23, 0.0.24, 0.0.25, 0.0.26, 0.0.27, 0.0.28, 0.0.29, 0.0.30, 0.0.31, 0.0.32, 0.0.33, 0.0.34)
  No matching distribution found for pantsbuild.pants==square-20150706-02

pip install of pantsbuild.pants failed!

Dry run release failed.

You can release by hand easily too,

./pants setup-py --recursive src/python/pants:pants-packaged

... but looking at the script

I believe you want

0.0.34.postN