The second parameter specifies how the file should be shared. If
    <code>SmbFile.FILE_NO_SHARE</code> is specified the client will
    have exclusive access to the file. An additional open command
    from jCIFS or another application will fail with the "file is being
    accessed by another process" error. The <code>FILE_SHARE_READ</code>,
    <code>FILE_SHARE_WRITE</code>, and <code>FILE_SHARE_DELETE</code> may be

        pdfResult.setExecutionTime(20);
        pdfResult.setHttpStatusCode(200);
        pdfResult.setLastModified(System.currentTimeMillis());
        pdfResult.setMethod("GET");
        pdfResult.setMimeType("application/pdf");
        pdfResult.setParentUrl("http://www.parent.com/");
        pdfResult.setRuleId("pdfRule");
        pdfResult.setSessionId(sessionId);
        pdfResult.setStatus(200);

    within the Covered Software, or any notices of licensing or any
    descriptive text giving attribution to any Contributor or the
    Initial Developer.

    3.4. Application of Additional Terms.

    You may not offer or impose any terms on any Covered Software in
    Source Code form that alters or restricts the applicable version of

    /**
     * The POST method.
     */
    protected static final String POST = "POST";

    /**
     * The MIME type.
     */
    protected String mimeType = "application/json";

    /**
     * Constructor.
     */
    public SearchApiManager() {
        setPathPrefix("/api/v1");
    }

    /**
     * Registers this API manager.
     */

  // These properties are initialized by connect() and never reassigned.

  /** The low-level TCP socket. */
  private var rawSocket: JavaNetSocket? = null

  /**
   * The application layer socket. Either an [SSLSocket] layered over [rawSocket], or [rawSocket]
   * itself if this connection does not use SSL.
   */
  internal var javaNetSocket: JavaNetSocket? = null
  private var handshake: Handshake? = null

In the wild, we've seen some objects set conventions in the object's constructor (3), but this can lead to unexpected assumptions or coupling between plugins.

For external plugins, it's difficult for an object to be used outside the application of a plugin, so following best practices is relatively straightforward.  For core plugins in gradle/gradle, it's easy for an object to be created without applying its associated plugin. For instance, Spring has a plugin that uses the Checkstyle...

/// warning

You most probably don't need these technical details.

These details are useful mainly if you had a FastAPI application older than 0.121.0 and you are facing issues with dependencies with `yield`.

///

    "path": "platforms/extensibility/plugin-use",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "plugins-application",
    "path": "platforms/jvm/plugins-application",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "plugins-distribution",

INFO:     Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
INFO:     Started reloader process [2248755] using WatchFiles
INFO:     Started server process [2248757]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
```

</div>

<details markdown="1">
<summary><code>fastapi dev</code> コマンドについて</summary>

     *   <tbody>
     *     <tr>
     *       <td>{@link ProjectScope#MAIN}</td>
     *       <td>{@code build.getOutputDirectory()}</td>
     *       <td>{@code target/classes}</td>
     *       <td>Compiled application classes and processed main resources</td>
     *     </tr>
     *     <tr>
     *       <td>{@link ProjectScope#TEST}</td>
     *       <td>{@code build.getTestOutputDirectory()}</td>