Closed jsirois closed 9 years ago
Assigning to @ericzundel cc @gmalmquist
I'd like to do the publish of Garrett's jarjar exit code fix in #5 via pants itself.
Any reason not to just import this to pantsbuild/pants?
Probably not - how about baby steps? I can publish Garretts fix in #5 then move.
That said - this was a good exercise in how hard is it to use pants - which we miss rolling things into pants.
FWIW - I patch these in like so curl -L https://github.com/pantsbuild/jarjar/pull/6.patch | git am
Do you need to initialize pushdb to some initial version? we've already published version 1.5
sorry wrong button
No - thats via --override=org.pantsbuild#jarjar=1.5.1
when I do the publish.
Wow, this is really awful (github pr) I agree with Stu and I think we should just pull it into pants proper too like we already did this with zinc. That leaves jmake out by its lonesome. I think we are all about to shed it anyway. But since you are ready to go with this, LGTM
Patched in @ 8a8bfbd3c0d91231df2fae2570beb7167826c46f
This kills the ant and maven setups as well as checked in jars and sets up the repo for maven-central publishing as well.