* Used for compilation, execution and Javadoc among others.
     * The Java tools location is {@link StandardLocation#CLASS_PATH}.
     *
     * <h4>Context-sensitive interpretation</h4>
     * A dependency with this path type will not necessarily be placed on the class path.
     * There are two circumstances where the dependency may nevertheless be placed somewhere else:
     *
     * <ul>

                                            <div class="modal-header">
                                                <h4 class="modal-title">
                                                    <la:message key="labels.rebuild_config_index"/>
                                                </h4>
                                                <button type="button" class="close" data-dismiss="modal"

</p>

<pre>
tmp := [n]T{x1, x2, … xn}
tmp[0 : n]
</pre>

<h4>Map literals</h4>

<p>
For map literals, each element must have a key.
For non-constant map keys, see the section on
<a href="#Order_of_evaluation">evaluation order</a>.
</p>

<h4>Elision of element types</h4>

<p>
Within a composite literal of array, slice, or map type <code>T</code>,

 *
 * <h4>Limited Inference for 4.0.0 Models (Maven 3.x POMs)</h4>
 * <ul>
 *   <li><strong>Child GroupId Removal</strong>: Removes child {@code <groupId>} when it matches parent groupId</li>
 *   <li><strong>Child Version Removal</strong>: Removes child {@code <version>} when it matches parent version</li>
 * </ul>
 *
 * <h4>Full Inference for 4.1.0+ Models</h4>
 * <ul>

                                                                            <h4 class="modal-title">
                                                                                <la:message
                                                                                        key="labels.crud_title_delete"/>
                                                                            </h4>

     * In the case of Java tools, the map may also contain {@code --patch-module} options, which are
     * {@linkplain org.apache.maven.api.JavaPathType#patchModule(String) handled in a special way}.
     *
     * <h4>Design note</h4>
     * All types of path are determined together because they are sometime mutually exclusive.
     * For example, an artifact of type {@value org.apache.maven.api.Type#JAR} can be placed

                                                <div class="modal-header">
                                                    <h4 class="modal-title">
                                                        <la:message key="labels.crud_title_delete"/>
                                                    </h4>
                                                    <button type="button" class="close" data-dismiss="modal"

 *         .transform(ActivityService::isLoggedIn, threadPool)
 *         .catching(RpcException.class, e -> false, directExecutor());
 * }
 *
 * <h3>Alternatives</h3>
 *
 * <h4>Frameworks</h4>
 *
 * <p>When chaining together a graph of asynchronous operations, you will often find it easier to
 * use a framework. Frameworks automate the process, often adding features like monitoring,

                                                <div class="modal-header">
                                                    <h4 class="modal-title">
                                                        <la:message key="labels.crud_title_delete"/>
                                                    </h4>
                                                    <button type="button" class="close" data-dismiss="modal"

                                                            <h4 class="modal-title">
                                                                <la:message
                                                                        key="labels.joblog_delete_all_link"/>
                                                            </h4>