stale-issue-label: "status:stale"
        days-before-stale: 0
        days-before-close: 30

---
name: Bug report
about: A reproducible problem
title: ''
labels: bug
assignees: ''

---

Good bug reports include a failing test! Writing a test helps you to isolate and describe the problem, and it helps us to fix it fast. Bug reports without a failing test or reproduction steps are likely to be closed.

Here’s an example test to get you started.

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.execution;

import org.apache.maven.artifact.versioning.ArtifactVersion;

/**
 * Describes runtime information about the application.
 *
 * @deprecated Use {@link org.apache.maven.rtinfo.RuntimeInformation} instead.
 */
@Deprecated
public interface RuntimeInformation {

        stale-issue-label: "status:stale"
        days-before-stale: 0
        days-before-close: 30

And your **FastAPI** application might also be composed of several files/modules, etc.

### **FastAPI** app file { #fastapi-app-file }

Let's say you have a file structure as described in [Bigger Applications](bigger-applications.md){.internal-link target=_blank}:

```
.
├── app
│   ├── __init__.py
│   └── main.py
```

In the file `main.py` you have your **FastAPI** app:

 * KIND, either express or implied.  See the License for the
 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.artifact.versioning;

/**
 * Describes an artifact version in terms of its components, converts it to/from a string and
 * compares two versions.
 *
 */
public interface ArtifactVersion extends Comparable<ArtifactVersion> {
    int getMajorVersion();

developer to create a plugin which means we would allow the direct use of a POM to state the dependencies of a given plugin and any tooling we created would be responsible for turning the dependency information in the POM into plugin metadata which described the dependencies of the plugin.

With respect to development inside an IDE the workspace from which we would like to resolve and retrieve dependencies is a read-only local repository to Mercury which is put at the front-end of the search...

 * {{{./apidocs/org/apache/maven/plugin/logging/Log.html}<<<Log>>> interface}} provides easy logging for the goal.

 []

 A plugin is described in a {{{../../api/maven-api-plugin/plugin.html}<<<META-INF/maven/plugin.xml>>> plugin descriptor}},
 generally generated from plugin sources using {{{/plugin-tools/maven-plugin-plugin/}maven-plugin-plugin}}.

* See Also

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.plugin.version;

import org.eclipse.aether.repository.ArtifactRepository;

/**
 * Describes the result of a plugin version resolution request.
 *
 * @since 3.0
 */
public interface PluginVersionResult {

    /**
     * The resolved plugin version.
     *

import java.util.List;

import org.apache.maven.execution.MavenExecutionRequest;
import org.apache.maven.project.MavenProject;
import org.apache.maven.project.ProjectBuildingException;

/**
 * Describes strategies for finding projects that Maven could build.
 */
public interface ProjectCollectionStrategy {
    /**
     *
     * @param request
     * @return
     * @throws ProjectBuildingException
     */