mirror of
https://github.com/ethauvin/kobalt-doc.git
synced 2025-04-25 03:57:11 -07:00
Fix sections.
This commit is contained in:
parent
4248eab785
commit
45716813ce
1 changed files with 16 additions and 16 deletions
|
@ -478,24 +478,24 @@ assemble {
|
||||||
ways to use <code>install</code>.
|
ways to use <code>install</code>.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<h3 class="section" id="install-target" indent="1">Bulk install</h3>
|
<h3 class="section" indent="2" id="install-target" indent="1">Bulk install</h3>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
The simplest way to install is either not specify anything in the <code>install</code> directive or an optional
|
The simplest way to install is either not specify anything in the <code>install</code> directive or an optional
|
||||||
<code>target</code> string, which specifies the target directory (<code>"libs"</code> by default):
|
<code>target</code> string, which specifies the target directory (<code>"libs"</code> by default):
|
||||||
</p>
|
</p>
|
||||||
<pre class="brush:java">
|
<pre class="brush:java">
|
||||||
install {
|
install {
|
||||||
target = "libs"
|
target = "libs"
|
||||||
}
|
}
|
||||||
</pre>
|
</pre>
|
||||||
<p>
|
|
||||||
With this approach, everything that was generated in <code>kobaltBuild/libs</code> gets copied to this
|
|
||||||
target directory.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<h3 class="section" id="install-include" indent="1">Fine grained install</h3>
|
<p>
|
||||||
|
With this approach, everything that was generated in <code>kobaltBuild/libs</code> gets copied to this
|
||||||
|
target directory.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<h3 class="section" indent="2" id="install-include" indent="1">Fine grained install</h3>
|
||||||
<p>
|
<p>
|
||||||
You can also be more selective in what you install with either the <code>copy</code> directive to copy
|
You can also be more selective in what you install with either the <code>copy</code> directive to copy
|
||||||
individual files or with <code>include</code>, which lets you specify more sophisticated ways of moving
|
individual files or with <code>include</code>, which lets you specify more sophisticated ways of moving
|
||||||
|
@ -508,14 +508,14 @@ assemble {
|
||||||
}
|
}
|
||||||
</pre>
|
</pre>
|
||||||
|
|
||||||
<div class="bs-callout bs-callout-warning">
|
<div class="bs-callout bs-callout-warning">
|
||||||
<h4>Note</h4>
|
<h4>Note</h4>
|
||||||
These two approaches are mutually exclusive: if you choose the fine grained approach, you will have to
|
These two approaches are mutually exclusive: if you choose the fine grained approach, you will have to
|
||||||
perform the installation of all the artifacts yourself and the <code>target</code> approach will
|
perform the installation of all the artifacts yourself and the <code>target</code> approach will
|
||||||
be ignored.
|
be ignored.
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
You might find the directive <code>collect()</code> useful when installing: this function is invoked on a
|
You might find the directive <code>collect()</code> useful when installing: this function is invoked on a
|
||||||
list of dependencies and returns a list of jar files that represent the transitive closure of the dependencies:
|
list of dependencies and returns a list of jar files that represent the transitive closure of the dependencies:
|
||||||
</p>
|
</p>
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue