Configuring the Axelix Build Plugin

Applying the Axelix build plugin stamps your build coordinates into the artifact so Axelix Master can identify the instance.

Applying the Axelix build plugin is the second half of making a service visible to Axelix Master — the first half is wiring up the starter. The plugin has nothing to configure: you apply it, and it stamps your build coordinates into the artifact so Master can identify the instance. See What is the Axelix build plugin? for what it produces and why it is required.

Required for registration

Master identifies every application by its groupId + artifactId. Without the plugin the META-INF/axelix-info.properties file is absent, the coordinates are blank, and Master rejects the registration — the instance never appears in the UI. The same coordinates also key the persistence insights (N+1 and entity-mapping analysis). Apply the plugin to every service you want Axelix to manage.

The plugins are currently published to Maven Central only. Publishing to the Gradle Plugin Portal is on the roadmap; until then, Gradle builds must resolve the plugin from Maven Central (see the pluginManagement block below). Keep the plugin version in sync with the starter version.

Apply the plugin

Because the plugin is not on the Gradle Plugin Portal yet, add mavenCentral() to pluginManagement in your settings.gradle.kts:

settings.gradle.kts
pluginManagement {
    repositories {
        gradlePluginPortal()
        mavenCentral()
    }
}

Then apply the plugin in build.gradle.kts:

build.gradle.kts
plugins {
    id("com.axelixlabs.axelix") version "1.0.0"
}

Neither plugin exposes any configuration options. The Gradle plugin only needs the standard project group and version to be set (it fails the build if group is blank, since Axelix needs it to tell applications apart); Maven always has its GAV coordinates, so nothing else is required.

On this page