forked from pantsbuild/pantsbuild.github.io
/
release_jvm.html
534 lines (512 loc) · 24.5 KB
/
release_jvm.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
<!DOCTYPE html>
<html lang="en">
<!--
Copyright 2014 Pants project contributors (see CONTRIBUTORS.md).
Licensed under the Apache License, Version 2.0 (see LICENSE).
-->
<head>
<meta charset="utf-8"/>
<title>JVM Artifact Release Process</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="shortcut icon" href="pants-logo.ico">
<!-- In case this is a "test publish", tell search engines where real version lives: -->
<link rel="canonical" href="http://pantsbuild.org/release_jvm.html">
<link rel="stylesheet" href="bootstrap-custom.min.css">
<link rel="stylesheet" href="bootstrap-custom-theme.min.css">
<link rel="stylesheet" href="docsite.css">
</head>
<body>
<div class="header">
<nav class="navbar navbar-default navbar-static-top">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand navbar-brand-img" href="index.html">
<img src="pants-logo.ico" alt="[pantsbuild logo]">
</a>
<a class="navbar-brand" href="index.html">
Pants
</a>
</div>
<div id="navbar" class="navbar-collapse collapse">
<ul class="nav navbar-nav navbar-right">
<li><a href="/">Docs</a></li>
<li><a href="community.html">Community</a></li>
<li><a href="https://www.github.com/pantsbuild/pants">GitHub</a></li>
<li>
<form class="navbar-form navbar-left search" role="search" action="https://www.google.com/search">
<div class="form-group">
<input type="text" name="as_q" class="form-control query" placeholder="Search">
<input name="as_sitesearch" value="pantsbuild.org" type="hidden">
</div>
</form>
</li>
</ul>
</div><!--/.nav-collapse -->
</div>
</nav>
</div>
<div class="page">
<div class="container-fluid">
<div class="row">
<div class="col-md-1">
</div>
<div class="col-md-2">
<div class="site-toc">
<ul>
<li class="toc-h1 toc-heading">
Getting Started
</li>
<li class="toc-h1 toc-link ">
<a href="install.html">Installing Pants</a>
</li>
<li class="toc-h1 toc-link ">
<a href="setup_repo.html">Setting Up Pants</a>
</li>
<li class="toc-h1 toc-link ">
<a href="first_tutorial.html">Tutorial</a>
</li>
<li class="toc-h1 toc-link ">
<a href="common_tasks.html">Common Tasks</a>
</li>
<li class="toc-h1 toc-heading">
Pants Basics
</li>
<li class="toc-h1 toc-link ">
<a href="why_use_pants.html">Why Use Pants?</a>
</li>
<li class="toc-h1 toc-link ">
<a href="first_concepts.html">Pants Concepts</a>
</li>
<li class="toc-h1 toc-link ">
<a href="build_files.html">BUILD files</a>
</li>
<li class="toc-h1 toc-link ">
<a href="target_addresses.html">Target Addresses</a>
</li>
<li class="toc-h1 toc-link ">
<a href="3rdparty.html">Third-Party Dependencies</a>
</li>
<li class="toc-h1 toc-link ">
<a href="options.html">Pants Options</a>
</li>
<li class="toc-h1 toc-link ">
<a href="invoking.html">Invoking Pants</a>
</li>
<li class="toc-h1 toc-link ">
<a href="reporting_server.html">Reporting Server</a>
</li>
<li class="toc-h1 toc-link ">
<a href="ide_support.html">IDE Support</a>
</li>
<li class="toc-h1 toc-heading">
JVM
</li>
<li class="toc-h1 toc-link ">
<a href="jvm_projects.html">JVM Projects with Pants</a>
</li>
<li class="toc-h1 toc-link ">
<a href="3rdparty_jvm.html">JVM 3rdparty Pattern</a>
</li>
<li class="toc-h1 toc-link ">
<a href="scala.html">Scala Support</a>
</li>
<li class="toc-h1 toc-link ">
<a href="publish.html">Publishing Artifacts</a>
</li>
<li class="toc-h1 toc-link ">
<a href="from_maven.html">Pants for Maven Experts</a>
</li>
<li class="toc-h1 toc-heading">
Python
</li>
<li class="toc-h1 toc-link ">
<a href="python_readme.html">Python Projects with Pants</a>
</li>
<li class="toc-h1 toc-link ">
<a href="3rdparty_py.html">Python 3rdparty Pattern</a>
</li>
<li class="toc-h1 toc-heading">
Go
</li>
<li class="toc-h1 toc-link ">
<a href="go_readme.html">Go support for Pants</a>
</li>
<li class="toc-h1 toc-heading">
Codegen
</li>
<li class="toc-h1 toc-link ">
<a href="thrift_deps.html">Thrift</a>
</li>
<li class="toc-h1 toc-heading">
Docgen
</li>
<li class="toc-h1 toc-link ">
<a href="page.html">Markdown</a>
</li>
<li class="toc-h1 toc-heading">
Getting Help
</li>
<li class="toc-h1 toc-link ">
<a href="tshoot.html">Troubleshooting</a>
</li>
<li class="toc-h1 toc-link ">
<a href="community.html">Community</a>
</li>
<li class="toc-h1 toc-heading">
Reference
</li>
<li class="toc-h1 toc-link ">
<a href="build_dictionary.html">Pants BUILD Dictionary</a>
</li>
<li class="toc-h1 toc-link ">
<a href="options_reference.html">Pants Reference</a>
</li>
<li class="toc-h1 toc-heading">
Release Notes
</li>
<li class="toc-h1 toc-link ">
<a href="notes-1.3.x.html">1.3.x Stable Releases</a>
</li>
<li class="toc-h1 toc-link ">
<a href="notes-1.2.x.html">1.2.x Stable Releases</a>
</li>
<li class="toc-h1 toc-link ">
<a href="notes-1.1.x.html">1.1.x Stable Releases</a>
</li>
<li class="toc-h1 toc-link ">
<a href="notes-1.0.x.html">1.0.x Stable Releases</a>
</li>
<li class="toc-h1 toc-link ">
<a href="notes-master.html">Master Pre-Releases</a>
</li>
<li class="toc-h1 toc-heading">
Developer
</li>
<li class="toc-h1 toc-link ">
<a href="dev.html">Pants Developer Center</a>
</li>
<li class="toc-h1 toc-link ">
<a href="export.html">Export Format</a>
</li>
</ul>
</div> <!-- site-toc -->
</div>
<div class="col-md-8">
<div class="content">
<div class="mainflow">
<nav class="pagetoc">
<ul>
<li class="toc-h1"><a href="#prerequisites">Prerequisites</a></li>
<li class="toc-h1"><a href="#dry-run">Dry Run</a></li>
<li class="toc-h1"><a href="#staging-to-ossrh">Staging to OSSRH</a></li>
<li class="toc-h1"><a href="#promoting-to-maven-central">Promoting to Maven Central</a></li>
<li class="toc-h1"><a href="#dogfood">Dogfood</a></li>
<li class="toc-h1"><a href="#releasers">Releasers</a></li>
</ul>
</nav>
<!-- main content start -->
<!-- generated by pants! -->
<style>
.codehilite .hll { background-color: #ffffcc }
.codehilite { background: #f0f0f0; }
.codehilite .c { color: #60a0b0; font-style: italic } /* Comment */
.codehilite .err { border: 1px solid #FF0000 } /* Error */
.codehilite .k { color: #007020; font-weight: bold } /* Keyword */
.codehilite .o { color: #666666 } /* Operator */
.codehilite .cm { color: #60a0b0; font-style: italic } /* Comment.Multiline */
.codehilite .cp { color: #007020 } /* Comment.Preproc */
.codehilite .c1 { color: #60a0b0; font-style: italic } /* Comment.Single */
.codehilite .cs { color: #60a0b0; background-color: #fff0f0 } /* Comment.Special */
.codehilite .gd { color: #A00000 } /* Generic.Deleted */
.codehilite .ge { font-style: italic } /* Generic.Emph */
.codehilite .gr { color: #FF0000 } /* Generic.Error */
.codehilite .gh { color: #000080; font-weight: bold } /* Generic.Heading */
.codehilite .gi { color: #00A000 } /* Generic.Inserted */
.codehilite .go { color: #808080 } /* Generic.Output */
.codehilite .gp { color: #c65d09; font-weight: bold } /* Generic.Prompt */
.codehilite .gs { font-weight: bold } /* Generic.Strong */
.codehilite .gu { color: #800080; font-weight: bold } /* Generic.Subheading */
.codehilite .gt { color: #0040D0 } /* Generic.Traceback */
.codehilite .kc { color: #007020; font-weight: bold } /* Keyword.Constant */
.codehilite .kd { color: #007020; font-weight: bold } /* Keyword.Declaration */
.codehilite .kn { color: #007020; font-weight: bold } /* Keyword.Namespace */
.codehilite .kp { color: #007020 } /* Keyword.Pseudo */
.codehilite .kr { color: #007020; font-weight: bold } /* Keyword.Reserved */
.codehilite .kt { color: #902000 } /* Keyword.Type */
.codehilite .m { color: #40a070 } /* Literal.Number */
.codehilite .s { color: #4070a0 } /* Literal.String */
.codehilite .na { color: #4070a0 } /* Name.Attribute */
.codehilite .nb { color: #007020 } /* Name.Builtin */
.codehilite .nc { color: #0e84b5; font-weight: bold } /* Name.Class */
.codehilite .no { color: #60add5 } /* Name.Constant */
.codehilite .nd { color: #555555; font-weight: bold } /* Name.Decorator */
.codehilite .ni { color: #d55537; font-weight: bold } /* Name.Entity */
.codehilite .ne { color: #007020 } /* Name.Exception */
.codehilite .nf { color: #06287e } /* Name.Function */
.codehilite .nl { color: #002070; font-weight: bold } /* Name.Label */
.codehilite .nn { color: #0e84b5; font-weight: bold } /* Name.Namespace */
.codehilite .nt { color: #062873; font-weight: bold } /* Name.Tag */
.codehilite .nv { color: #bb60d5 } /* Name.Variable */
.codehilite .ow { color: #007020; font-weight: bold } /* Operator.Word */
.codehilite .w { color: #bbbbbb } /* Text.Whitespace */
.codehilite .mf { color: #40a070 } /* Literal.Number.Float */
.codehilite .mh { color: #40a070 } /* Literal.Number.Hex */
.codehilite .mi { color: #40a070 } /* Literal.Number.Integer */
.codehilite .mo { color: #40a070 } /* Literal.Number.Oct */
.codehilite .sb { color: #4070a0 } /* Literal.String.Backtick */
.codehilite .sc { color: #4070a0 } /* Literal.String.Char */
.codehilite .sd { color: #4070a0; font-style: italic } /* Literal.String.Doc */
.codehilite .s2 { color: #4070a0 } /* Literal.String.Double */
.codehilite .se { color: #4070a0; font-weight: bold } /* Literal.String.Escape */
.codehilite .sh { color: #4070a0 } /* Literal.String.Heredoc */
.codehilite .si { color: #70a0d0; font-style: italic } /* Literal.String.Interpol */
.codehilite .sx { color: #c65d09 } /* Literal.String.Other */
.codehilite .sr { color: #235388 } /* Literal.String.Regex */
.codehilite .s1 { color: #4070a0 } /* Literal.String.Single */
.codehilite .ss { color: #517918 } /* Literal.String.Symbol */
.codehilite .bp { color: #007020 } /* Name.Builtin.Pseudo */
.codehilite .vc { color: #bb60d5 } /* Name.Variable.Class */
.codehilite .vg { color: #bb60d5 } /* Name.Variable.Global */
.codehilite .vi { color: #bb60d5 } /* Name.Variable.Instance */
.codehilite .il { color: #40a070 } /* Literal.Number.Integer.Long */
</style>
<h1 id="jvm-artifact-release-process">JVM Artifact Release Process</h1>
<p>This page describes how to make a versioned release of the Pants jvm
tools to Maven Central.</p>
<p>Releasing jvm tools largely follows the
<a href="publish.html">standard jar publishing process</a>, but has
some non-standard initial one-time setup.</p>
<p>At a high level, releasing pants jvm artifacts involves:</p>
<ul>
<li>Deciding when to release.
At present this is ad-hoc, typically when
a change has been made to a tool and the author wants to use a
version incorporating that change.</li>
<li>(optional) Perform a release <a href="#dry-run">dry run</a>.</li>
<li><a href="#staging-to-ossrh">Staging</a> the release to OSSRH.</li>
<li><a href="#promoting-to-maven-central">Promoting</a> the release to Maven Central.</li>
<li><a href="#dogfood">Dogfood</a> the release.</li>
</ul>
<h2 id="prerequisites">Prerequisites</h2>
<p>You must be at least a
<a href="https://github.com/orgs/pantsbuild/teams/committers">committer</a> in
the pantsbuild GitHub organisation to publish pants artifacts. If you
aren't yet, you need only ping the
<a href="https://groups.google.com/forum/#!forum/pants-devel">pants-devel</a>
group to inquire about getting a release performed.</p>
<p>If you are a committer, there are four additional requirements to
satisfy in order to be able publish to Maven Central:</p>
<ul>
<li>
<p>Create and publish a pgp key if you don't already have a published
pgp key. There is nothing Maven Central specific about this, but
Sonatype does provide
<a href="http://central.sonatype.org/pages/working-with-pgp-signatures.html">some instructions</a>
you might follow.</p>
</li>
<li>
<p><a href="https://issues.sonatype.org/secure/Signup!default.jspa">Create a sonatype.org JIRA account</a>
if you don't already have one.</p>
</li>
<li>
<p>Ask an existing Pants Maven Central <a href="#releasers">releaser</a> to
create a sonatype.org JIRA ticket to get you added to the
org.pantsbuild maintainers. You'll need to give them your
sonatype.org JIRA account id. Here's an
<a href="https://issues.sonatype.org/browse/OSSRH-12754">example ticket</a>
they can use as a template. Once this is done and you've performed
your 1st release, add yourself to the <a href="#releasers">Releasers</a>
section below.</p>
</li>
<li>
<p>Create a <code>~/.config/pants/release/jvm/pgp.properties</code> file to store the
credentials Pants needs to sign artifacts uploaded to sonatype.org.
This process is <a href="#pgp-credentials">described below</a>.</p>
</li>
<li>
<p>Create an entry in your <code>~/.netrc</code> file to enable authentication to Sonatype.</p>
<div class="codehilite"><pre>machine oss.sonatype.org
login jsirois
password XYX
</pre></div>
</li>
</ul>
<h3 id="pgp-credentials">PGP Credentials</h3>
<p>Artifacts released to Maven Central must be pgp-signed. In order to
sign artifacts, the pants jar publishing process currently needs access
to your pgp key passphrase via file (There is an issue
<a href="https://github.com/pantsbuild/pants/issues/1407">here</a> tracking a better
solution).</p>
<p>First you'll need to create a secure
<a href="https://docs.oracle.com/javase/6/docs/api/java/util/Properties.html#load(java.io.Reader)">java properties file</a>
to hold your pgp credentials:</p>
<div class="codehilite"><pre><span class="nv">$ </span>mkdir -p ~/.config/pants/release/jvm <span class="o">&&</span> <span class="se">\</span>
touch ~/.config/pants/release/jvm/pgp.properties <span class="o">&&</span> <span class="se">\</span>
chmod 600 ~/.config/pants/release/jvm/pgp.properties
</pre></div>
<p>The properties file supports the following keys with noted defaults if omitted:</p>
<ul>
<li>
<p><code>pgp.secring</code></p>
<p>Assumes your pgp implementation is gpg and defaults to <code>~/.gnupg/secring.gpg</code></p>
</li>
<li>
<p><code>pgp.keyid</code></p>
<p>Defaults to <code>auto</code>. If you're unsure which pgp key <code>auto</code> will
select and you use gpg, you can determine the key id and verify the
passphrase in one fell swoop with the following command:</p>
<div class="codehilite"><pre><span class="nv">$ </span>killall gpg-agent; <span class="nb">echo</span> | gpg --sign -vv >/dev/null
gpg: using PGP trust model
gpg: key 67B5C626: accepted as trusted key
gpg: no running gpg-agent - starting <span class="s1">'/usr/bin/gpg-agent'</span>
gpg: waiting <span class="k">for </span>the agent to come up ... <span class="o">(</span>5s<span class="o">)</span>
gpg: connection to agent established
<span class="o">[</span>pinentry prompts <span class="k">for </span>passphrase<span class="o">]</span>
gpg: writing to stdout
gpg: RSA/SHA256 signature from: <span class="s2">"67B5C626 John Sirois <john.sirois@gmail.com>"</span>
</pre></div>
<p>In this case the default key id is <code>67B5C626</code>. You can add an entry
to the properties file instead of relying on the default <code>auto</code>
setting if you prefer to be explicit like so:</p>
<div class="codehilite"><pre><span class="nv">$ </span><span class="nb">echo </span>pgp.keyid<span class="o">=</span>67B5C626 >> ~/.config/pants/release/jvm/pgp.properties
</pre></div>
</li>
<li>
<p><code>pgp.password</code></p>
<p><strong>This key is required</strong>, you must use the passphrase of the pgp
key identified by <code>pgp.keyid</code> as the value. If you did not specify
a <code>pgp.keyid</code> then this should be the passphrase for your default
pgp key.</p>
</li>
</ul>
<h2 id="dry-run">Dry Run</h2>
<p>Releases should only be published from master, so get on master and
ensure the changes you want to publish are present. After confirming
this, you can test out the publish in 2 ways:</p>
<ol>
<li>
<p>A dry run to get a preview of what will be published and why:</p>
<div class="codehilite"><pre><span class="nv">$ </span>./pants clean-all publish.jar src/<span class="o">{</span>java,scala<span class="o">}</span>::
</pre></div>
</li>
<li>
<p>A local publish to get a preview of both what will be published
and why as well as the changelogs:</p>
<div class="codehilite"><pre><span class="nv">$ </span>./pants clean-all publish.jar --no-publish-jar-dryrun --local<span class="o">=</span>/tmp/m2 src/<span class="o">{</span>java,scala<span class="o">}</span>::
</pre></div>
<p>Note that this "dry-run" technique somewhat confusingly passes
<code>--no-publish-jar-dryrun</code> but only because the publish is local and to a
temporary dir (the argument to <code>--local</code>). You can also poke
around in the <code>/tmp/m2</code> local maven repo if you're curious or want
to double-check fine details of exactly what will be pushed.</p>
</li>
</ol>
<h2 id="staging-to-ossrh">Staging to OSSRH</h2>
<p>When you're ready to publish to Maven Central, the 1st step is to
publish the jvm tool jars to Sonatype's OSSRH staging repository. Note
that nothing will actually go live until the staging repository is
<a href="#promoting-to-maven-central">released by you later</a>, so this step has
no consequences of global importance. Pants will create and push git
tags for the staging releases you do here, but in the worst case the
tags will point to releases never promoted to Maven Central, which is
fine.</p>
<p>To do the staging release, it's a normal pants publish and it's easiest
to use the following command, which will publish everything that's
changed and only those things that have changed since the last publish:</p>
<div class="codehilite"><pre><span class="nv">$ </span>./pants publish.jar --no-publish-jar-dryrun src/<span class="o">{</span>java,scala<span class="o">}</span>::
</pre></div>
<h2 id="promoting-to-maven-central">Promoting to Maven Central</h2>
<p>With the jvm tools published to the Sonatype OSSRH staging repository,
you'll need to complete the release using Sonatype's OSSRH Nexus
repository manager web UI. Sonatype describes the process
<a href="http://central.sonatype.org/pages/releasing-the-deployment.html">here</a>
but the process is also described below:</p>
<ol>
<li>
<p>Log into Sonatype's OSSRH Nexus repository manager web UI.</p>
<p>You do this <a href="https://oss.sonatype.org/#stagingRepositories">here</a>.
You should use the the same user id and password you use to login
to the Sonatype JIRA server.</p>
</li>
<li>
<p>Find the staging repository auto-created when you
<a href="#staging-to-ossrh">staged the release</a> above.</p>
<p>As shown below, in the 'Staging Repositories' tab enter
<code>pantsbuild</code> in the search box in the upper-right corner to filter
the display to your staging repository.</p>
<p><img alt="image" src="images/ossrh-publish-find-staging-repo.png"/></p>
<p>There should be exactly one repository listed and you should
select its checkbox.</p>
</li>
<li>
<p>Close the selected staging repository.</p>
<p>As shown below, with the staging repository selected, there will
be a 'Close' button available. Look for in in the menu bar across
the top of the repository list. Click it.</p>
<p><img alt="image" src="images/ossrh-publish-close-staging-repo.png"/></p>
<p>This will trigger a validation process that checks the staged
artifacts for signatures, a valid POM and more. When validation is
complete, you'll receive an email from nexus@oss.sonatype.org with
the subject 'Nexus: Staging Completed'. You may need to click the
'Refresh' button in the UI to see the 'Close' button transition to
a disabled state and the 'Release' button to its right transition
to an enabled state.</p>
</li>
<li>
<p>Release the selected staging repository.</p>
<p>As shown below, with the staging repository selected and closed,
there will be a 'Release' button available. Click it.</p>
<p><img alt="image" src="images/ossrh-publish-release-staging-repo.png"/></p>
<p>This will trigger another round of artifact validation and another
email, this time with subject 'Nexus: Promotion Completed'. At
this point you're all done and just need to wait ~10 minutes for
the artifacts to be available in Maven Central and ~2 hours to show
up in the
<a href="http://search.maven.org/#search%7Cga%7C1%7Corg.pantsbuild">search index</a>.</p>
</li>
</ol>
<h2 id="dogfood">Dogfood</h2>
<p>Check Maven Central to ensure everything looks good. You can browse the
<a href="https://repo1.maven.org/maven2/org/pantsbuild">org.pantsbuild subtree</a>
to find the artifact(s) you just released. Once available you can send
out an RB bumping the versions of the released tools in <code>BUILD.tools</code>.</p>
<h2 id="releasers">Releasers</h2>
<p>The following folks are set up to publish to Maven Central for
org.pantsbuild:</p>
<ul>
<li>David Turner <a href="mailto:dturner@twopensource.com">dturner@twopensource.com</a></li>
<li>Eric Ayers <a href="mailto:ericzundel@gmail.com">ericzundel@gmail.com</a></li>
<li>John Sirois <a href="mailto:john.sirois@gmail.com">john.sirois@gmail.com</a></li>
<li>Stu Hood <a href="mailto:stuhood@gmail.com">stuhood@gmail.com</a></li>
</ul>
<!-- main content end -->
<div class="generated">
Generated by <a href="docs.html">publish_docs</a>
from dist/markdown/html/src/docs/release_jvm.html 2017-05-29T10:30:51.064086
</div>
</div> <!-- mainflow -->
</div> <!-- content -->
</div>
<div class="col-md-1">
</div>
</div> <!-- row -->
</div> <!-- container-fluid -->
</div> <!-- page -->
<script src="https://code.jquery.com/jquery-2.2.3.min.js" integrity="sha384-I6F5OKECLVtK/BL+8iSLDEHowSAfUo76ZL9+kGAgTRdiByINKJaqTPH/QVNS1VDb" crossorigin="anonymous"></script>
<script src="bootstrap-custom.min.js"></script>
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-78111411-1', 'auto');
ga('send', 'pageview');
</script>
</body>
</html>