# nx-quarkus
[](https://www.npmjs.com/package/@nxrocks/nx-quarkus)
[](https://github.com/tinesoft/nxrocks/actions?query=workflow%3ARelease)
[](https://github.com/semantic-release/semantic-release)
> Nx Plugin to generate, run, package, build (and more) [Quarkus](https://quarkus.io) projects inside your Nx workspace
## Contents
- [Features](#features)
- [Setup](#setup)
- [Generators](#generators)
- [Executors](#executors)
- [Compatibility with Nx](#compatibility-with-nx)
## Features
Here is a list of some of the coolest features of the plugin:
- ✅ Generation of Quarkus applications/libraries based on **Quarkus app generator** API
- ✅ Building, packaging, testing, etc your Quarkus projects
- ✅ 🆕 Built-in support for creating [**multi-modules**](recipes/README.md#creating-multi-modules-quarkus-projects) Quarkus projects with both `Maven` and `Gradle`
- ✅ Built-in support for code formatting using the excellent [**Spotless**](https://github.com/diffplug/spotless) plugin for `Maven` or `Gradle`
- ✅ Built-in support for **corporate proxies** (either via `--proxyUrl` or by defining environment variable `http_proxy`, `HTTP_PROXY`, `https_proxy` or `HTTPS_PROXY`)
- ✅ Integration with Nx's **dependency graph** (through `nx graph` or `nx affected:graph`): this allows you to **visualize** the dependencies of any Quarkus's `Maven`/`Gradle` applications or libraries inside your workspace, just like Nx natively does it for JS/TS-based projects!
_Example of running the `nx graph` command on a workspace with 2 Quarkus projects inside_
- ...
## Setup
📢 ℹ️ 🆕 HEADS UP! New simplified setup since October 2023, with our custom CLI!
> You can now use our own `create-nx-quarkus` **CLI** to easily create a Nx workspace, that comes with this plugin pre-installed!
>
> Simply run:
>
> ```
> # npm
> npx create-nx-quarkus@latest
> # or
> # yarn
> yarn create nx-quarkus
> ```
>
> and you are good to go‧o‧o‧o! 🚀
>
> More information here: [create-nx-quarkus](../packages/create-nx-quarkus/README.md)
Otherwise, this is the traditional way of setting things up:
### 1. Creating the Nx workspace
If you have not already, [create an Nx workspace](https://nx.dev/getting-started/nx-setup) with the following:
```
# npm
npx create-nx-workspace@latest
# yarn
yarn create nx-workspace
```
### 2. Installing the Plugin
Then you need to install the plugin in order to generate Quarkus applications later on.
```
# npm
npm install @nxrocks/nx-quarkus --save-dev
# yarn
yarn add @nxrocks/nx-quarkus --dev
```
## Generators
This plugin is composed of 2 main **generators**:
- `project` generator
- `link` generator
### Generating Project (`project` generator)
Simply run the `project` generator with the following command:
```
nx g @nxrocks/nx-quarkus:project path/to/your/app-name
```
> you can also use the following aliases to call the generator: `proj`, `new`, or `create`
You will be prompted for entering the most commonly customized generation options (like project's `groupId`, `artifactId`, `packaging`, `dependencies`, etc).
To skip the interactive prompt, or if you want to customize all non-prompted options, you can pass them along directly when running the command, as such:
```
nx g @nxrocks/nx-quarkus:project path/to/your/app-name --optionName1 optionValue1 ... --optionNameN optionValueN
```
#### Generation Options
Here the list of available generation options :
| Arguments | Description |
| ------------- | --------------------------------- |
| `` | The directory of the new project. |
| Option | Value | Description |
| --------------------------- | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `projectType` | `application` \| `library` | Type of project to generate |
| `buildSystem` | `MAVEN` \| `GRADLE` | Build system |
| `groupId` | `string` | GroupId of the project |
| `artifactId` | `string` | ArtifactId of the project |
| `skipFormat` | `boolean` | Do not add the ability to format code (using Spotless plugin) |
| `extensions` | `string` | List of extensions to use (comma-separated). Go to [recipes](recipes/README.md#adding-quarkus-dependencies) for more information |
| `transformIntoMultiModule` | `boolean` | Transform the project into a multi-module project. Go to [recipes](recipes/README.md#creating-multi-modules-quarkus-projects) for more information |
| `addToExistingParentModule` | `boolean` | Add the project into an existing parent module project. Go to [recipes](recipes/README.md#creating-multi-modules-quarkus-projects) for more information |
| `parentModuleName` | `string` | Name of the parent module to create or to add child project into. Go to [recipes](recipes/README.md#creating-multi-modules-quarkus-projects) for more information |
| `keepProjectLevelWrapper` | `boolean` | Keep the `Maven` or `Gradle` wrapper files from child project (when generating a multi-module project). Go to [recipes](recipes/README.md#creating-multi-modules-quarkus-projects) for more information |
| `quarkusInitializerUrl` | `https://code.quarkus.io` | URL to the Quarkus Initializer instance to use |
| `proxyUrl` | | The URL of the (corporate) proxy server to use to access Quarkus Initializer |
| `skipeCodeSamples` | `string` | Whether or not to include code samples from extensions (when available) |
| `tags` | `string` | Tags to use for linting (comma-separated) |
| `directory` | `string` | Directory where the project is placed |
| `javaVersion` | `string \| number` | The java version of the project (currently supports versions 17 and 21) |
> **Note:** If you are working behind a corporate proxy, you can use the `proxyUrl` option to specify the URL of that corporate proxy server.
> Otherwise, you'll get a [ETIMEDOUT error](https://github.com/tinesoft/nxrocks/issues/125) when trying to access official Quarkus Initializer to generate the project.
> Even simpler, you can just define environment variable `http_proxy`, `HTTP_PROXY`, `https_proxy` or `HTTPS_PROXY` globally.
### Linking Projects (`link` generator)
This generator is used to link a Quarkus project inside the workspace (the _source_ project) with another project (the \__target_ project), by adding the source project as an **implicit dependency** of the later.
Simply run the `link` generator with the following command:
```
nx g @nxrocks/nx-quarkus:link
```
> you can also use the following aliases to call the generator: `link-project`
You will be prompted for entering the most commonly customized generation options (`sourceProjectName`, `targetProjectName`).
To skip the interactive prompt, you can pass options along directly when running the command, as such:
```
nx g @nxrocks/nx-quarkus:link --sourceProjectName --targetProjectName
```
or even simpler:
```
nx g @nxrocks/nx-quarkus:link
```
#### Generation Options
Here the list of available generation options :
| Arguments | Description |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| `` | The name of the source(Quarkus) project to link from. 1st argument of the `link` generator. Can also be provided as option `--sourceProjectName` |
| `` | The name of the target project to link to. 2nd argument of the `link` generator. Can also be provided as option `--targetProjectName` |
## Executors
Once your app is generated, you can now use **executors** to manage it.
Here the list of available executors:
| Executor | Arguments | Description |
| ------------------------- | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `run` \| `dev` \| `serve` | `ignoreWrapper:boolean`, `runFromParentModule:boolean`, `args: string[]` | Runs the project in dev mode using either `./mvnw\|mvn quarkus:dev` or `./gradlew\|gradle quarkusDev` |
| `remote-dev` | `ignoreWrapper:boolean`, `runFromParentModule:boolean`, `args: string[]` | Runs the project in remote dev mode using either `./mvnw\|mvn quarkus:remote-dev` or `./gradlew\|gradle quarkusRemoteDev` |
| `build` | `ignoreWrapper:boolean`, `runFromParentModule:boolean`, `args: string[]` | Builds a native or container friendly image either `./mvnw\|mvn build` or `./gradlew\|gradle build` |
| `test` | `ignoreWrapper:boolean`, `runFromParentModule:boolean`, `args: string[]` | Tests the project using either `./mvnw\|mvn test` or `./gradlew\|gradle test` |
| `clean` | `ignoreWrapper:boolean`, `runFromParentModule:boolean`, `args: string[]` | Cleans the project using either `./mvnw\|mvn clean` or `./gradlew\|gradle clean` |
| `format` | `ignoreWrapper:boolean`, `runFromParentModule:boolean`, `args: string[]` | Format the project using [Spotless](https://github.com/diffplug/spotless) plugin for Maven or Gradle |
| `package` | `ignoreWrapper:boolean`, `runFromParentModule:boolean`, `args: string[]` | Packages the project using either `./mvnw\|mvn package` or `./gradlew\|gradle package` |
| `install` | `ignoreWrapper:boolean`, `runFromParentModule:boolean`, `args: string[]` | Installs the project's artifacts to local Maven repository (in `~/.m2/repository`) using either `./mvnw\|mvn install` or `./gradlew\|gradle publishToMavenLocal` |
| `add-extension` | `ignoreWrapper:boolean`, `runFromParentModule:boolean`, `args: string[]` | Adds a new extension to the project using either `./mvnw\|mvn quarkus:add-extension` or `./gradlew\|gradle quarkusAddExtension` |
| `list-extensions` | `ignoreWrapper:boolean`, `runFromParentModule:boolean`, `args: string[]` | Adds a new extension to the project using either `./mvnw\|mvn quarkus:list-extensions` or `./gradlew\|gradle quarkusListExtensions` |
In order to execute the requested command, each executor will use, by default, the embedded `./mvnw` or `./gradlew` executable, that was generated alongside the project.
If you want to rely on a globally installed `mvn` or `gradle` executable instead, add the `--ignoreWrapper` option to bypass it.
This can be useful in a CI environment for example, or in a restricted environment where the binary cannot be downloaded (due to proxy/firewall limitations).
You can pass in additional arguments to the underlying Gradle or Maven, either temporarily (via `--args="..."`). For example:
```
nx remote-dev your-quarkus-app --args="-Dquarkus.live-reload.url=http://my-remote-host:8080"
```
Or, permanently by editing the related executor in the `workspace.json` file, as such:
```js
{
"version": 1,
"projects": {
"your-quarkus-app": {
"projectType": "application",
"root": "apps/your-quarkus-app",
"sourceRoot": "apps/your-quarkus-app/src",
"targets": {
"remote-dev": {
"executor": "@nxrocks/nx-quarkus:remote-dev",
"options": {
"root": "apps/your-quarkus-app",
"args": ["-Dquarkus.live-reload.url=http://my-remote-host:8080"]// your additional args here
}
}
}
}},
"cli": {
"defaultCollection": "@nx/workspace"
}
}
```
### Running the project in dev mote - (`dev` or `serve` Executors)
```
nx serve your-quarkus-app
// or
nx dev your-quarkus-app
```
### Install the project's artifacts to local Maven repository (in `~/.m2/repository`) - (`install` Executor)
```
nx install your-quarkus-app
```
### Running the project in remote dev mode - (`remote-dev` Executor)
```
// for a maven-based project
nx remote-dev your-quarkus-app --args="-Dquarkus.live-reload.url=http://my-remote-host:8080"
// for a gradle-based project
nx remote-dev your-quarkus-app --args="-Dquarkus.live-reload.url=http://my-remote-host:8080"
```
### Building the aplication - (`build` Executor)
```
nx build your-quarkus-app
```
> **Note:** a task dependency to `install` executor of dependent (library) projects [is added by the plugin](https://github.com/tinesoft/nxrocks/commit/a18a9aaaeb92a779b98dfb82fdf72ac702c7ca34), so that Nx will automatically `install` dependent artifacts to your local Maven repository, prior to running this command. This is particulaly useful, when for example, you have a Spring Boot **application** that depends on another Spring boot **library** in the workspace. No more need to install the library yourself first!
### Testing the project - (`test` Executor)
```
nx test your-quarkus-app
```
### Cleaning the project - (`clean` Executor)
```
nx clean your-quarkus-app
```
### Formatting the project - (`format` Executor)
```
nx run your-quarkus-app:format
// or its simpler alias
nx apply-format your-quarkus-app
```
> Note: You \*cannot\*\* use the shorter `nx format your-boot-app` syntax here, because that would conflict with the native `format` command from Nx CLI.
### Packaging the project - (`package` Executor)
```
nx package your-quarkus-app
```
### Add Extension the project - (`add-extension` Executor)
```
// for a maven-based project
nx add-extension your-quarkus-app --args="-Dextensions=resteasy,hibernate-validator"
// for a gradle-based project
nx add-extension your-quarkus-app --args="--extensions=resteasy,hibernate-validator"
```
### List Extensions in the project - (`list-extensions` Executor)
```
nx list-extensions your-quarkus-app
```
## Compatibility with Nx
Every Nx plugin relies on the underlying Nx Workspace/DevKit it runs on. This table provides the compatibility matrix between major versions of Nx workspace and this plugin.
| Plugin Version | Nx Workspace version |
| -------------- | -------------------- |
| `>=v9.x.x` | `>=v20.x.x` |
| `>=v8.x.x` | `>=v18.x.x` |
| `>=v7.x.x` | `>=v17.x.x` |
| `>=v6.x.x` | `>=v16.x.x` |
| `>=v5.x.x` | `>=v15.8.x` |
| `>=v4.x.x` | `>=v15.x.x` |
| `>=v2.1.x` | `>=v13.8.x` |
| `>=v2.x.x` | `>=v12.6.x` |
| `>=v1.x.x` | `>=v11.x.x` |
## License
Copyright (c) 2021-present Tine Kondo. Licensed under the MIT License (MIT)