forked from pantsbuild/pantsbuild.github.io
/
first_concepts.html
462 lines (439 loc) · 22.3 KB
/
first_concepts.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
<!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>Pants Concepts</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/first_concepts.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 toc-here">
Pants Concepts
</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="#goals-and-tasks">Goals and Tasks</a></li>
<li class="toc-h1"><a href="#targets">Targets</a></li>
<li class="toc-h1"><a href="#target-types">Target Types</a></li>
<li class="toc-h1"><a href="#addresses">Addresses</a></li>
<li class="toc-h1"><a href="#what-pants-does">What Pants Does</a></li>
<li class="toc-h1"><a href="#next-step">Next Step</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="pants-concepts">Pants Concepts</h1>
<p>To use Pants effectively, it helps to understand a few concepts:</p>
<ul>
<li><strong>Goals</strong> help users tell pants what actions to take</li>
<li><strong>Tasks</strong> are the pants modules that run actions</li>
<li><strong>Targets</strong> describe what files to take those actions upon</li>
<li><strong>Target types</strong> define the types of operations that can be performed on
a target</li>
<li><strong>Addresses</strong> describe the location of a target in the repo</li>
</ul>
<h2 id="goals-and-tasks">Goals and Tasks</h2>
<p><strong>Goals</strong> are the "verbs" of Pants. When you invoke Pants, you name
goals on the command line to say what Pants should do. For example, to
run tests, you would invoke Pants with the <code>test</code> goal. To create a
bundle--an archive containing a runnable binary and resource
files--you would invoke Pants with the <code>bundle</code> goal.</p>
<p><strong>Tasks</strong> actually perform the work. When you invoke a goal, it finds
all the tasks needed to make that goal work. Sometimes, there is a one
to one mapping between a task name and a goal name, but often multiple tasks
are registered in a goal. For example, the <code>junit</code>
task runs tests for JVM projects. It is registered in the <code>test</code>
goal and sometimes referred to as <code>test.junit</code>.</p>
<p>In a nutshell, goals are the way users specify tasks. Sometimes goals
are helpful groupings of tasks to make it easier for users to tell
pants what they want to do.</p>
<p>Tasks can depend on other tasks. When you invoke a goal in
Pants, it builds a list of dependent tasks that need to be executed
first. So, when you invoke the <code>test</code> goal, it will also invoke the
tasks in the <code>gen</code>, <code>resolve</code> and <code>compile</code> goals, because tasks for
code generation, artifact resolution, and compilation need to occur
before a test can be run. To find out more about how task dependencies
are computed, read about <em>product types</em> in
<a href="dev_tasks.html">Developing a Pants Task</a>.</p>
<h2 id="targets">Targets</h2>
<p><strong>Targets</strong> are the "nouns" of Pants, things pants can act upon. You
annotate your source code with <code>BUILD</code> files to define these
targets. For example, if your <code>tests/com/twitter/mybird/</code> directory
contains JUnit tests, you have a <code>tests/com/twitter/mybird/BUILD</code> file
with a <code>junit_tests</code> target definition. As you change your source code,
you'll occasionally change the set of Targets by editing <code>BUILD</code> files.
E.g., if you refactor some code, moving part of it to a new directory,
you'll probably set up a new <code>BUILD</code> file with a target to build that
new directory's code.</p>
<p>Targets can "depend" on other targets. For example, if your <code>foo</code> code
imports code from another target <code>bar</code>, then <code>foo</code> depends on <code>bar</code>. You
specify this dependency in <code>foo</code>'s target definition in its <code>BUILD</code>
file. If you invoke Pants to compile <code>foo</code>, it "knows" it also needs to
compile <code>bar</code>, and does so.</p>
<h2 id="target-types">Target Types</h2>
<p><strong>Target Types</strong> describe the kind of target to be operated on. Each
Pants build target has a <em>type</em>, such as <code>java_library</code> or
<code>python_binary</code>. Tasks choose to work on particular targets by
selecting the target types they are interested in from the build
graph.</p>
<p>For a list of all Target types (and other things that can go in <code>BUILD</code>
files), see the <a href="build_dictionary.html">BUILD Dictionary</a>.
The following list describes the most common target types:</p>
<p><strong>Library Targets</strong><br>
To define an "importable" thing, you want a library target type, such as
<code>java_library</code> or <code>python_library</code>. Another target whose code imports a
library target's code should list the library target in its
<code>dependencies</code>.</br></p>
<p><strong>Binary Targets</strong><br>
To define a "runnable" thing, you want a <code>jvm_binary</code> or <code>python_binary</code>
target. A binary probably has a <code>main</code> and dependency libraries. (We encourage a
binary's main to be separate from the libraries it uses to run, if any.)</br></p>
<p><strong>External Dependencies</strong><br>
Not everything is source code is in your repository. Your targets can
depend on <code>.jar</code>s or <code>.whl</code>s from elsewhere.</br></p>
<p><strong>Test Targets</strong><br>
To define a collection of tests, you want a <code>junit_tests</code> or
<code>python_tests</code> target. The test target depends upon the targets whose
code it tests. This isn't just logical, it's handy, too: you can
compute dependencies to figure out what tests to run if you change some
target's code.</br></p>
<h2 id="addresses">Addresses</h2>
<p><strong>Addresses</strong> describe the location of a target in the build
graph. The address has two parts: the directory to the BUILD file
and the name of the target within that BUILD file.</p>
<p>For example, if you have a <code>tests/com/twitter/mybird/BUILD</code> file
with a <code>junit_tests(name='test-flight)</code> target definition, you would
write the address as:</p>
<div class="codehilite"><pre>tests/com/twitter/mybird:test-flight
</pre></div>
<p>You use an address whenever you specify a target to build on the
command line or when one target depends on another in a BUILD file.
To find out more about addresses, see
<a href="target_addresses.html">Target Addresses</a>.</p>
<h2 id="what-pants-does">What Pants Does</h2>
<p>When you invoke Pants, you specify goals (actions to take) and targets
(things to act upon).</p>
<p><strong>Pants plans a list of tasks.</strong> You specify one or more goals on the
command line. Pants finds the tasks needed to complete that goal.
Pants knows that some tasks depend on others. If you
invoke Pants with, say, the <code>test</code> goal to test some code, Pants knows
it must first compile code; before it can compile code, it needs to
resolve artifact dependencies and generate code from IDL files (e.g.,
Thrift). Pants thus generates a topologically-sorted list of goals and
tasks to perform, a
<em>build execution plan</em>. This plan might look something like</p>
<div class="codehilite"><pre>./pants --explain <span class="nb">test </span>src/java::
Goal Execution Order:
bootstrap -> imports -> unpack-jars -> deferred-sources -> gen
-> jvm-platform-validate -> resolve -> compile -> resources -> <span class="nb">test</span>
</pre></div>
<p>Pants does <em>not</em> consider targets while planning; some of these tasks
might thus turn out to be no-ops. E.g., Pants might plan a <code>gen</code>
(generate code) task even if you don't, in fact, use any generated code.</p>
<p><strong>Pants computes a target dependencies graph.</strong> It starts with the
target[s] you specify on the command line. It notes which targets they
depend on, which targets those targets depend on, which targets <em>those</em>
targets depend on, and so on.</p>
<p><strong>Pants then attempts to carry out its planned tasks.</strong> It proceeds goal
by goal. If it has a problem carrying out one task, it does not continue
to the others. (Thus, if you attempt to test targets <em>A</em> and <em>B</em>,
but there's a compilation error in <em>A</em>, then Pants won't test <em>B</em> even
if it compiled fine.)</p>
<p>For each task in the plan, Pants executes that task to all
targets in its computed dependency tree[s]. It starts with
depended-upon targets and works its way up to depending targets. Each
Pants target has a type; Pants uses this to determine how to apply a
task to that target. In many cases, applying a task to a target is a
no-op. In the more interesting cases, Pants does something. It
probably invokes other tools. For example, depending on the code in
the relevant targets, that "compile" goal might invoke <code>javac</code> a few
times and <code>scalac</code>.</p>
<p>Pants caches things it builds. Thus, if you change one source file and
re-build, Pants probably doesn't "build the world." It just builds a few
things. Pants keys its cache on hashed file contents. This is a
straightforward way to build the right things after some files' contents
change. (It <em>can</em> surprise you if you <code>touch</code> a file, start a compile,
and nothing happens. If you want to, e.g., see <code>Foo.java</code>'s compile
warnings again, instead of using <code>touch</code>, you might append a newline.)</p>
<h2 id="next-step">Next Step</h2>
<p>If you're ready to give Pants a try, go to
<a href="first_tutorial.html">First Tutorial</a>.</p>
<!-- main content end -->
<div class="generated">
Generated by <a href="docs.html">publish_docs</a>
from dist/markdown/html/src/docs/first_concepts.html 2017-05-29T10:30:50.538620
</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>