forked from pantsbuild/pantsbuild.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path3rdparty_jvm.html
562 lines (538 loc) · 33 KB
/
3rdparty_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
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
<!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 3rdparty Pattern</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/3rdparty_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 toc-here">
JVM 3rdparty Pattern
</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="#3rdpartyjvm">3rdparty/jvm</a></li>
<li class="toc-h1"><a href="#your-codes-build-file">Your Code's BUILD File</a></li>
<li class="toc-h1"><a href="#round-trip-dependencies">"Round Trip" Dependencies</a></li>
<li class="toc-h1"><a href="#controlling-jar-dependency-versions">Controlling JAR Dependency Versions</a></li>
<li class="toc-h1"><a href="#managing-transitive-dependencies">Managing Transitive Dependencies</a></li>
<li class="toc-h2"><a href="#the-problem">The Problem</a></li>
<li class="toc-h2"><a href="#possible-solutions">Possible Solutions</a></li>
<li class="toc-h2"><a href="#managed-jar-dependencies">Managed Jar Dependencies</a></li>
<li class="toc-h1"><a href="#using-a-snapshot-jvm-dependency">Using a SNAPSHOT JVM Dependency</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-3rdparty-pattern">JVM 3rdparty Pattern</h1>
<p>In general, we recommend the <a href="3rdparty.html">3rdparty idiom</a>
for organizing dependencies on code from outside the source tree. This document
describes how to make this work for JVM (Java or Scala) code.</p>
<p>Your JVM code can depend on external, third-party libraries. Pants uses
<a href="http://ant.apache.org/ivy/">Ivy</a> to resolve and retrieve these JAR files.
You should know the (<a href="http://maven.apache.org/guides/mini/guide-central-repository-upload.html">Maven/Ivy groupId, artifactId, and
version</a>)
you want to use.</p>
<h2 id="3rdpartyjvm">3rdparty/jvm</h2>
<p>If you have a small to medium number of third-party dependencies, you can define
them all in a single <code>3rdparty/jvm/BUILD</code> file. If you have a large number, it
may make sense to organize them in multiple subdirectories, say by category or by publisher.</p>
<p>In the appropriate <code>BUILD</code> file, you create a <a href="build_dictionary.html#bdict_jar_library" pantsref="bdict_jar_library"><code>jar_library</code></a>
referencing the <a href="build_dictionary.html#bdict_jar" pantsref="bdict_jar"><code>jar</code></a>s you want:</p>
<p>
<div class="md-included-snippet"><div class="codehilite"><pre><span class="n">jar_library</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s">'junit'</span><span class="p">,</span>
<span class="n">jars</span><span class="o">=</span><span class="p">[</span>
<span class="n">jar</span><span class="p">(</span><span class="s">'junit'</span><span class="p">,</span> <span class="s">'junit'</span><span class="p">,</span> <span class="s">'4.12'</span><span class="p">)</span>
<span class="p">],</span>
<span class="c"># junit is frequently used only for its annotations.</span>
<span class="n">scope</span><span class="o">=</span><span class="s">'forced'</span><span class="p">,)</span>
</pre></div></div>
</p>
<p>Here, the <a href="build_dictionary.html#bdict_jar_library" pantsref="bdict_jar_library"><code>jar_library</code></a>'s name
defines a target address that other build targets can refer to. The
<a href="build_dictionary.html#bdict_jar" pantsref="bdict_jar"><code>jar</code></a>s refer to jars that Ivy can resolve and fetch.</p>
<h2 id="your-codes-build-file">Your Code's BUILD File</h2>
<p>To set up your code to import the external jar, you add a dependency to
the appropriate Java target[s] in your <code>BUILD</code> file and add <code>import</code>
statements in your Java code.</p>
<p>For example, your <code>BUILD</code> file might have</p>
<p>
<div class="md-included-snippet"><div class="codehilite"><pre> <span class="n">dependencies</span><span class="o">=</span><span class="p">[</span>
</pre></div></div>
</p>
<p>And your Java code might have:</p>
<div class="codehilite"><pre><span class="kn">import</span> <span class="nn">org.junit.Test</span><span class="o">;</span>
</pre></div>
<h2 id="round-trip-dependencies">"Round Trip" Dependencies</h2>
<p>It is possible for your code to exist as source in the repo but
also be published as a binary to an external repository. If you happen to pull in any
third party artifacts, they may express a dependency on the published
version of the artifact. This means that the classpath will contain
both the version in the repo compiled from source and an older version
that was previously published. In this case, you want to be sure that
when pants always prefers the version built from source.</p>
<p>Fortunately, the remedy for this is simple. If you add a <code>provides=</code>
parameter that matches the one used to publish the artifact, pants
will always prefer the local target definition to the
published jar.</p>
<div class="codehilite"><pre><span class="n">jar_library</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s">'api'</span><span class="p">,</span>
<span class="n">sources</span> <span class="o">=</span> <span class="n">globs</span><span class="p">(</span><span class="s">'*.java'</span><span class="p">),</span>
<span class="n">provides</span> <span class="o">=</span> <span class="n">artifact</span><span class="p">(</span><span class="n">org</span><span class="o">=</span><span class="s">'org.archie'</span><span class="p">,</span>
<span class="n">name</span><span class="o">=</span><span class="s">'api'</span><span class="p">,</span>
<span class="n">repo</span><span class="o">=</span><span class="n">myrepo</span><span class="p">,)</span>
<span class="p">)</span>
</pre></div>
<h2 id="controlling-jar-dependency-versions">Controlling JAR Dependency Versions</h2>
<p><strong>If you notice that one "foreign" dependency pulls in mostly wrong
things,</strong> tell Pants not to pull in its dependencies. In your
<code>3rdparty/.../BUILD</code> file, use <code>jar</code>'s <code>intransitive</code> argument; then
carefully add hand-picked versions:</p>
<div class="codehilite"><pre><span class="n">jar_library</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s">"retro-naming-factory"</span><span class="p">,</span>
<span class="n">jars</span><span class="o">=</span><span class="p">[</span>
<span class="n">jar</span><span class="p">(</span><span class="n">org</span><span class="o">=</span><span class="s">'retro'</span><span class="p">,</span> <span class="n">name</span><span class="o">=</span><span class="s">'retro-factory'</span><span class="p">,</span> <span class="n">rev</span><span class="o">=</span><span class="s">'5.0.18'</span><span class="p">,</span> <span class="n">intransitive</span><span class="o">=</span><span class="bp">True</span><span class="p">),</span>
<span class="p">],</span>
<span class="n">dependencies</span><span class="o">=</span><span class="p">[</span>
<span class="c"># Don't use retro's expected (old, incompatible) common-logging</span>
<span class="c"># version, yipe; use the same version we use everywhere else:</span>
<span class="s">'3rdparty/jvm/common-logging'</span><span class="p">,</span>
<span class="p">]</span>
<span class="p">)</span>
</pre></div>
<p><strong>If you notice a small number of transitive dependencies to exclude</strong>
Rather than mark the <code>jar</code> intransitive, you can <code>exclude</code> some
transitive dependencies from JVM targets:</p>
<div class="codehilite"><pre><span class="n">java_library</span><span class="p">(</span><span class="n">name</span> <span class="o">=</span> <span class="s">'loadtest'</span><span class="p">,</span>
<span class="n">dependencies</span> <span class="o">=</span> <span class="p">[</span>
<span class="s">'3rdparty/storm:storm'</span><span class="p">,</span>
<span class="p">],</span>
<span class="n">sources</span> <span class="o">=</span> <span class="n">globs</span><span class="p">(</span><span class="s">'*.java'</span><span class="p">),</span>
<span class="n">excludes</span> <span class="o">=</span> <span class="p">[</span>
<span class="n">exclude</span><span class="p">(</span><span class="s">'org.sonatype.sisu.inject'</span><span class="p">,</span> <span class="s">'cglib'</span><span class="p">)</span>
<span class="p">]</span>
<span class="p">)</span>
</pre></div>
<h2 id="managing-transitive-dependencies">Managing Transitive Dependencies</h2>
<h3 id="the-problem">The Problem</h3>
<p>If you have jars that pull in many transitive dependencies, you probably
want to constrain which versions of those transitive dependencies you
pull in. This is valuable for:</p>
<ul>
<li>Security concerns (you may want to avoid artifacts with known
vulnerabilities, or you may only want to use particular jars which you
trust).</li>
<li>Predictable and consistent behavior across all projects in your
repository (described below).</li>
<li>Caching concerns/build times (described below).</li>
</ul>
<p>Otherwise, you may have some targets that end up being built with
version <code>1.2.3</code> of a transitive dependency, and others that get built with
<code>4.5.6</code> of that dependency. Worse, the <em>same target</em> might be built with
different versions of a transitive dependency depending on what other
targets happen to be part of the same pants invocation. To illustrate
this, consider the diagram below:</p>
<div>
<img alt="image" src="images/transitive-dependencies.png" style="display: block; max-height: 25ex; margin-left: auto; margin-right: auto;">
</img></div>
<p>Assume <code>foo</code> and <code>bar</code> are binary targets. If you build a binary of <code>foo</code>
with <code>./pants binary foo</code>, <code>foo</code> will be packaged with the <code>example</code> jar
in addition to its transitive dependencies, which will be resolved as the
<code>common</code> jar, version <code>1.2.3</code>.</p>
<p>Likewise, if you run <code>./pants binary bar</code>, it will be packaged with <code>demo</code>,
and the transitive dependencies of <code>demo</code>, which here is simply the <code>common</code>
jar version <code>4.5.6</code>.</p>
<p>However, if you run <code>./pants binary foo bar</code>, ivy will only resolve one
version of <code>common-1.2.3</code>, which most likely means that both <code>foo</code> and <code>bar</code>
will get <code>common</code> version <code>4.5.6</code> (because it is the more recent version).
This is a problem, because it may be that <code>common-4.5.6</code> is not compatible
with <code>3rdparty:example</code>, which will <em>break the <code>foo</code> binary at runtime</em>.</p>
<p>More subtly, if you have many intermediate <code>java_library</code> targets between
your <code>jvm_binaries</code> and your <code>jar_library</code> targets (which is normaly the
case), simply changing which combination of <code>java_library</code> targets are in
the same <code>./pants</code> invocation may invalidate the cache and force Pants to
recompile them, even if their sources are unchanged. This is because they
may resolve different versions of their transitive jar dependencies than
the previous time they were compiled, which means their classpaths will be
different. Getting a different classpath causes a cache-miss, forcing a
recompile. In general recompiling when the classpath changes is the
correct thing to do, however this means that unstable transitive
dependencies will cause a lot of cache-thrashing. If you have a large
repository with a large amount of code, recompiles get expensive.</p>
<h3 id="possible-solutions">Possible Solutions</h3>
<p>There are a few ways to avoid or work around these problems. A simple method
is to use the <a href="http://ant.apache.org/ivy/history/2.4.0/settings/conflict-managers.html">strict ivy conflict manager</a>,
which will cause the jar resolution to fail with an error if it detects two
artifacts with conflicting versions. This has the advantage of forcing a dev
to be aware of (and make a decision about) confliction versions.</p>
<p>You could also disable transitive jar resolution altogether, and explicitly
declare every dependency you need. This ensures that you have total control
over your external dependencies, but can be difficult to maintain.</p>
<p>The third option is using <code>managed_jar_dependencies</code>, to pin the versions of
the subset of your transitive dependencies that you care about.</p>
<h3 id="managed-jar-dependencies">Managed Jar Dependencies</h3>
<p>Maven handles this problem with the <code><dependencyManagement></code>
<a href="https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management">stanza</a>,
and Pants has similar functionality via the <code>managed_jar_dependencies</code> target.</p>
<p>You can set up your <code>3rdparty/BUILD</code> file like so:</p>
<div class="codehilite"><pre><span class="n">managed_jar_dependencies</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s">'management'</span><span class="p">,</span>
<span class="n">artifacts</span><span class="o">=</span><span class="p">[</span>
<span class="s">':commons-io'</span><span class="p">,</span>
<span class="s">':jersey-core'</span><span class="p">,</span>
<span class="p">],</span>
<span class="p">)</span>
<span class="n">jar_library</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s">'commons-io'</span><span class="p">,</span>
<span class="n">jars</span><span class="o">=</span><span class="p">[</span>
<span class="n">jar</span><span class="p">(</span><span class="s">'commons-io'</span><span class="p">,</span> <span class="s">'commons-io'</span><span class="p">,</span> <span class="s">'2.5'</span><span class="p">),</span>
<span class="p">],</span>
<span class="p">)</span>
<span class="n">jar_library</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s">'jersey-core'</span><span class="p">,</span>
<span class="n">jars</span><span class="o">=</span><span class="p">[</span>
<span class="n">jar</span><span class="p">(</span><span class="s">'com.sun.jersey'</span><span class="p">,</span> <span class="s">'jersey-core'</span><span class="p">,</span> <span class="s">'1.19.1'</span><span class="p">),</span>
<span class="p">],</span>
<span class="p">)</span>
</pre></div>
<p>And in <code>pants.ini</code>, add:</p>
<div class="codehilite"><pre><span class="k">[jar-dependency-management]</span>
<span class="err">default_target:</span> <span class="err">3rdparty:management</span>
</pre></div>
<p>This will force all <code>jar_library</code> targets in your repository to use the
versions of <code>commons-io</code> and <code>jersey-core</code> referenced by the <code>management</code>
target. When resolving transitive dependencies, Pants will always choose
the versions "pinned" by the managed dependencies target.</p>
<p>If a <code>jar_library</code> omits the version for one of its <code>jar()</code>s, it will use
the version defined in <code>managed_jar_dependencies</code>. If a <code>jar()</code> defines a
version that <em>conflicts</em> with the version set in <code>managed_jar_dependencies</code>,
an error will be raised and the build will fail (though this behavior can
be modified via the <code>conflict_strategy</code> option).</p>
<p>This is a bit verbose, and entails a bit of duplicate code (you have to
mention <code>jersey-core</code> 3 times in the above example). You can use the
<code>managed_jar_libraries</code> target factory instead to make your <code>3rdparty/BUILD</code>
definitions more concise.</p>
<p>This example is equivalent to the one earlier, but using <code>managed_jar_libraries</code>
instead:</p>
<div class="codehilite"><pre><span class="n">managed_jar_libraries</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s">'management'</span><span class="p">,</span>
<span class="n">artifacts</span><span class="o">=</span><span class="p">[</span>
<span class="n">jar</span><span class="p">(</span><span class="s">'commons-io'</span><span class="p">,</span> <span class="s">'commons-io'</span><span class="p">,</span> <span class="s">'2.5'</span><span class="p">),</span>
<span class="n">jar</span><span class="p">(</span><span class="s">'com.sun.jersey'</span><span class="p">,</span> <span class="s">'jersey-core'</span><span class="p">,</span> <span class="s">'1.19.1'</span><span class="p">),</span>
<span class="p">],</span>
<span class="p">)</span>
</pre></div>
<p>This automatically generates <code>jar_library</code> targets for you, and makes a
<code>managed_jar_dependencies</code> target to reference them. (Note that you still
need to make the same change to pants.ini).</p>
<p>The generated library targets follow the naming convention
<code>org.name.classifier.ext</code>, where <code>classifier</code> and <code>ext</code> are omitted if they
are the default values.</p>
<p>So in the above example will generate two <code>jar_library</code> targets, called
<code>3rdparty:commons-io.commons-io</code> and <code>3rdparty:com.sun.jersey.jersey-core</code>.</p>
<p>The artifacts list of <code>managed_jar_libraries</code> can also accept target
addresses to already-existing <code>jar_libraries</code>, just like a normal
<code>managed_jar_dependences</code> target. In this case, <code>managed_jar_libraries</code>
will just use the referenced target, rather than generating a new one.</p>
<p>With Pants you can create <em>multiple</em> <code>managed_jar_dependencies</code>.
If you have more than one, for any particular <code>jar_library</code>, you can define
which <code>managed_jar_dependencies</code> it uses explicitly (rather than using the
default defined in <code>pants.ini</code>):</p>
<div class="codehilite"><pre><span class="n">jar_library</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s">'org.apache.hadoop-alternate'</span><span class="p">,</span>
<span class="n">jars</span><span class="o">=</span><span class="p">[</span>
<span class="n">jar</span><span class="p">(</span><span class="s">'org.apache.hadoop'</span><span class="p">,</span> <span class="s">'hadoop-common'</span><span class="p">,</span> <span class="s">'2.7.0'</span><span class="p">),</span>
<span class="p">],</span>
<span class="n">managed_dependencies</span><span class="o">=</span><span class="s">'3rdparty:management-alternate'</span><span class="p">,</span>
<span class="p">)</span>
</pre></div>
<p><a id="test_3rdparty_jvm_snapshot" pantsmark="test_3rdparty_jvm_snapshot"> </a></p>
<h2 id="using-a-snapshot-jvm-dependency">Using a SNAPSHOT JVM Dependency</h2>
<p>Sometimes your code depends on a buggy external JVM dependency. You
think you've fixed the external code, but want to test locally before
uploading it to make sure. To do this, in the <code>jar</code> dependency for the
artifact, specify the <code>url</code> attribute to point to the local file and
change the <code>rev</code>. If you are actively making changes to the dependency,
you can also use the <code>mutable</code> jar attribute to re-import the file each
time pants is run (otherwise, pants will cache it):</p>
<div class="codehilite"><pre><span class="n">jar_library</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s">'checkstyle'</span><span class="p">,</span>
<span class="n">jars</span> <span class="o">=</span> <span class="p">[</span>
<span class="n">jar</span><span class="p">(</span><span class="n">org</span><span class="o">=</span><span class="s">'com.puppycrawl.tools'</span><span class="p">,</span> <span class="n">name</span><span class="o">=</span><span class="s">'checkstyle'</span><span class="p">,</span> <span class="n">rev</span><span class="o">=</span><span class="s">'5.5-SNAPSHOT'</span><span class="p">,</span>
<span class="n">url</span><span class="o">=</span><span class="s">'file:///Users/pantsdev/Src/checkstyle/checkstyle.jar'</span><span class="p">,</span>
<span class="n">mutable</span><span class="o">=</span><span class="bp">True</span><span class="p">),</span>
<span class="p">],</span>
<span class="p">)</span>
</pre></div>
<!-- main content end -->
<div class="generated">
Generated by <a href="docs.html">publish_docs</a>
from dist/markdown/html/examples/src/java/org/pantsbuild/example/3rdparty_jvm.html 2017-05-29T10:30:52.019208
</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>