> For the complete documentation index, see [llms.txt](https://hayston.gitbook.io/flp-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hayston.gitbook.io/flp-wiki/developer-documentation/build.md).

# Build, test and contribute

## Build the project

Clone the repository and use its Gradle wrapper from the root directory. Gradle requires **JDK 25**; the build uses other Java toolchains as needed.

{% tabs %}
{% tab title="Windows" %}

```powershell
.\gradlew.bat build --console=plain
```

{% endtab %}

{% tab title="macOS / Linux" %}

```sh
./gradlew build --console=plain
```

{% endtab %}
{% endtabs %}

`build` runs the project's tests and checks. For work on one module, use a targeted task such as `./gradlew :velocity:build`.

## Contribute

Open issues or pull requests against the [FastLoginPlus repository](https://github.com/Hayston1001/FastLoginPlus). Describe the purpose of the change, affected platforms and checks you actually ran. Do not commit server data or secrets.

Before making changes, see the [architecture overview](/flp-wiki/developer-documentation/architecture.md) and [contribution guide](https://github.com/Hayston1001/FastLoginPlus/blob/main/CONTRIBUTING.md). When changing user-facing behavior, update the relevant configuration, messages and English and Chinese documentation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hayston.gitbook.io/flp-wiki/developer-documentation/build.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.