Maven Central
Firefly 1.0.1 is published to Maven Central under the io.github.fishered namespace. Spring Boot applications only need the Starter and do not need a private repository or separate Firefly module declarations.
Browse firefly-spring-boot-starter 1.0.1 on Maven Central
Indexing delay
Search results and regional mirrors can take some time to synchronize after a Central Portal release. The Maven coordinates remain unchanged during this period.
Maven
<dependency>
<groupId>io.github.fishered</groupId>
<artifactId>firefly-spring-boot-starter</artifactId>
<version>1.0.1</version>
</dependency>Maven Central is Maven's default repository, so no additional <repositories> entry is required.
Gradle
repositories {
mavenCentral()
}
dependencies {
implementation "io.github.fishered:firefly-spring-boot-starter:1.0.1"
}Published modules
The Starter resolves its required modules through the published POM dependency chain:
| Artifact | Responsibility |
|---|---|
scheduler-core | Scheduling domain model, routing, and storage contracts |
plugin-api | Extension API for external plugins |
netty | Protocol and transport shared by Gateway and Executor |
executor-netty | Netty Executor client used by business services |
firefly-spring-boot-autoconfigure | Executor, job annotation, and Spring lifecycle auto-configuration |
firefly-spring-boot-starter | Single integration entry point for Spring Boot applications |
Applications should not declare these modules separately. Depend on a lower-level artifact directly only when developing a custom transport, client, or plugin.
Verify dependencies
Refresh Maven metadata and inspect the dependency tree:
mvn -U dependency:treeThe resolved tree should include firefly-spring-boot-starter, firefly-spring-boot-autoconfigure, executor-netty, netty, and scheduler-core.
Version policy
Released Maven Central versions are immutable. Upgrades must use an explicit new version; later fixes will continue to use new patch releases.