import static java.util.Objects.nonNull;

/**
 * Pseudo test to generate documentation fragment about supported CLI options. TODO such documentation generation code
 * should not be necessary as unit test but should be run during site generation (Velocity? Doxia macro?)
 */
class CLIManagerDocumentationTest {
    private static final String LS = System.lineSeparator();

    private static class OptionComparator implements Comparator<Option> {

	// Limits all body and header sizes to a maximum fixed limit
	setRequestLimitMiddleware,
	// Validate all the incoming requests.
	setRequestValidityMiddleware,
	// Add upload forwarding middleware for site replication
	setUploadForwardingMiddleware,
	// Add bucket forwarding middleware
	setBucketForwardingMiddleware,
	// Add new middlewares here.
}

// configureServer handler returns final handler for the http server.

  // PEM files for root certificates of Comodo and Entrust. These two CAs are sufficient to view
  // https://publicobject.com (Comodo) and https://squareup.com (Entrust). But they aren't
  // sufficient to connect to most HTTPS sites including https://godaddy.com and https://visa.com.
  // Typically developers will need to get a PEM file from their organization's TLS administrator.

  ).int().default(DEFAULT_TIMEOUT)

  val followRedirects: Boolean by option("-L", "--location", help = "Follow redirects").flag()

  val allowInsecure: Boolean by option("-k", "--insecure", help = "Allow connections to SSL sites without certs").flag()

  val showHeaders: Boolean by option("-i", "--include", help = "Include protocol headers in the output").flag()

						>
						</a>
					</div>
					</c:if>
					<div class="description">${doc.content_description}</div>
				</div>
				<div class="site text-truncate">
					<c:if test="${clipboardCopyIcon}"><i class="far fa-copy url-copy" data-clipboard-text="${doc.url_link}"></i></c:if>
					<cite>${f:h(doc.site_path)}</cite>
				</div>
				<div class="more">

      },
      "label": {
        "type": "keyword"
      },
      "virtual_host": {
        "type": "keyword"
      },
      "segment": {
        "type": "keyword"
      },
      "site": {
        "type": "keyword"
      },
      "title": {
        "type": "text",
        "analyzer": "standard_analyzer",
        "search_analyzer": "standard_search_analyzer",

                -->
                <argument>--templates=maven-configuration.md,configuration.properties,configuration.yaml</argument>
                <argument>${basedir}/..</argument>
                <argument>${basedir}/../src/site/markdown/</argument>
              </arguments>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

  <profiles>
    <profile>

              </models>
              <version>2.0.0</version>
            </configuration>
          </execution>
          <execution>
            <id>modello-site-docs</id>
            <phase>none</phase>
          </execution>
        </executions>
      </plugin>
      <plugin>
        <groupId>com.github.siom79.japicmp</groupId>

      },
      "label": {
        "type": "keyword"
      },
      "virtual_host": {
        "type": "keyword"
      },
      "segment": {
        "type": "keyword"
      },
      "site": {
        "type": "keyword"
      },
      "title": {
        "type": "text",
        "analyzer": "standard_analyzer",
        "search_analyzer": "standard_search_analyzer",

<h2>검색방법</h2>
<dl>
	<dt>필드 지정 검색</dt>
	<dd>
		필드 이름 뒤에 콜론 :에 지정된 모든 필드에서 검색 할 수 있습니다.
		예를 들어, 문서의 title 필드에서 Fess가 포함 된 문서를 검색하려면 다음과 같이 입력합니다.
		<pre>title:Fess</pre>
		기본으로 사용 가능한 필드는 url, host, site, title content,
		content_length, last_modified 및 mimetype입니다.
		설정에서 지정하는 필드는 변경할 수 있습니다.
	</dd>
	<dt>정렬</dt>
	<dd>
		sort 연산자는 지정된 필드 이름으로 문서를 정렬합니다.
		sort 연산자의 사용 방법은 sort:&lt;field&gt;.&lt;order&gt;입니다.