* referral level and target path for which DFS resolution is requested.
 *
 * @author mbechler
 */
public class DfsReferralRequestBuffer implements Encodable {

    private final int maxReferralLevel;
    private final String path;

    /**
     * Constructs a DFS referral request buffer
     *
     * @param filename the DFS path to request referral for

    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.gwt.core.Core" />
<inherits name="com.google.gwt.user.User" />

    public void test_generate_invalid_parent_directory() throws Exception {
        // Create a path that's guaranteed to be invalid
        final File invalidParent = System.getProperty("os.name", "linux").toLowerCase().startsWith("windows")
                ? new File("Q:\\invalid\\path\\that\\does\\not\\exist")
                : new File("/invalid/path/that/does/not/exist");
        final File outputFile = new File(invalidParent, "output.txt");

     *
     * @param path the HTML path to process
     * @return the processed path with virtual host handling applied
     */
    protected HtmlNext virtualHost(final HtmlNext path) {
        return ComponentUtil.getVirtualHostHelper().getVirtualHostPath(path);
    }

     * @param path      The file path of the dictionary.
     * @param timestamp The last modified timestamp of the file.
     * @return A new {@link SynonymFile} associated with the dictionary manager.
     */
    @Override
    protected DictionaryFile<? extends DictionaryItem> newDictionaryFile(final String id, final String path, final Date timestamp) {

            Path file = context.cwd.resolve(cliOptions.atFile().orElseThrow());
            if (Files.isRegularFile(file)) {
                result.add(parseMavenAtFileOptions(file));
            } else {
                throw new IllegalArgumentException("Specified file does not exists (" + file + ")");
            }
        }
        // maven.config; if exists

    }

    @Override
    public UpgradeResult doApply(UpgradeContext context, Map<Path, Document> pomMap) {
        Set<Path> processedPoms = new HashSet<>();
        Set<Path> modifiedPoms = new HashSet<>();
        Set<Path> errorPoms = new HashSet<>();

        for (Map.Entry<Path, Document> entry : pomMap.entrySet()) {
            Path pomPath = entry.getKey();
            Document pomDocument = entry.getValue();

    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.common.base.Base" />
<inherits name="com.google.gwt.core.Core" />

/// tip | 豆知識

`swagger_ui_redirect` 用の *path operation* は、OAuth2 を使用する場合の補助です。

API を OAuth2 プロバイダと統合すると、認証を実行して取得したクレデンシャルを持った状態で API ドキュメントに戻れます。そして実際の OAuth2 認証を用いてドキュメント上から API と対話できます。

Swagger UI がこの処理を裏側で行いますが、そのためにこの「redirect」の補助が必要です。

///

### テスト用の *path operation* を作成 { #create-a-path-operation-to-test-it }

すべてが動作するかをテストできるように、*path operation* を作成します:

    public BaseApiManager() {
        // Default constructor
    }

    /**
     * Gets the path prefix for API endpoints.
     * @return The path prefix.
     */
    public String getPathPrefix() {
        return pathPrefix;
    }

    /**
     * Sets the path prefix for API endpoints.
     * @param pathPrefix The path prefix to set.
     */
    public void setPathPrefix(final String pathPrefix) {