kill job argument to BDGSparkCommand

[ryan-williams]

fixes #37

I think this should be merge-able whenever, though the corresponding version-bump in ADAM will have to go along with the corresponding refactor over there, which I have locally built off of ADAM#664 and will file shortly, for merging whenever we're ready to actually do that upgrade, or cut a branch that includes backwards-incompatible changes from bdg-utils-0.2.1

[fnothaft]

Will merge as soon as build runs. I can cut a release after it merges, so that we can get it in to ADAM. I'll update bigdatagenomics/adam#664 with the 0.2.1 release. Do you want to PR your changes against my bigdatagenomics/adam#664 branch? That might be the cleanest way to do things.

[AmplabJenkins]

Merged build triggered.

[AmplabJenkins]

Merged build started.

[AmplabJenkins]

Merged build finished. Test PASSed.

[AmplabJenkins]

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/bdg-utils-prb/42/
Test PASSed.

[fnothaft]

Merged! Thanks @ryan-williams!

[ryan-williams]

haha, I was about to PR my changes against your #664 and apologize for the complexity of that; glad you think that is "the cleanest way" :)

I build mvn installd my utils:0.2.1-SNAPSHOT with this PR merged in and am building ADAM against that local utils:0.2.1-SNAPSHOT. As soon as that passes I'll send my PR against #664.

[fnothaft]

haha, I was about to PR my changes against your #664 and apologize for the complexity of that; glad you think that is "the cleanest way" :)

Great minds... ;)

I build mvn installd my utils:0.2.1-SNAPSHOT with utils#38 merged in and am building ADAM against that local utils:0.2.1-SNAPSHOT. As soon as that passes I'll send my PR against #664.

Sounds great. I'm starting the release process now.