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

     * 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

                                    </h3>
                                </div>
                                <div class="card-body">
                                    <h4>${f:h(displayFileName)}</h4>
                                    <div>
                                        <la:errors property="content"/>
                                        <la:textarea styleId="content" property="content" rows="20"

The following table describes the minimum language version required for
features introduced after Go 1.
</p>

<h4 id="Go_1.9">Go 1.9</h4>
<ul>
<li>
An <a href="#Alias_declarations">alias declaration</a> may be used to declare an alias name for a type.
</li>
</ul>

<h4 id="Go_1.13">Go 1.13</h4>
<ul>
<li>

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

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

                                                    <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,

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

     * The path elements are separated by an option-specific or platform-specific separator.
     * If the given {@code paths} argument contains no element, then this method returns an empty string.
     *
     * <h4>Examples</h4>
     * If {@code paths} is a list containing two elements, {@code dir/path1} and {@code dir/path2}, then:
     *
     * <ul>
     *   <li>If this type is {@link JavaPathType#MODULES}, then this method returns