Backend Development 4 min read

How mica-auto Simplifies Spring Boot Starter Configuration in Mica Microservices

The article explains the purpose, usage scenarios, features, dependency setup, build process, and licensing of mica-auto, a component that generates essential Spring Boot starter configurations for the Mica microservice framework, helping avoid package inconsistencies and streamline development.

Java Architecture Diary
Java Architecture Diary
Java Architecture Diary
How mica-auto Simplifies Spring Boot Starter Configuration in Mica Microservices
mica-auto

is a basic component of the

Spring Cloud

microservice framework

Mica

, used to generate some default Spring Boot starter configurations.

Usage Scenarios

It mainly avoids inconsistencies between the main Spring Boot project package and sub‑projects or sub‑modules, preventing package‑scan issues.

Custom

spring boot starter

.

Sub‑projects in multi‑module projects (not recommended to add

mica-auto

to the main project).

Features

Generate

spring.factories

.

Generate

spring-devtools.properties

.

Generate

FeignClient

entries in

spring.factories

for automatic Feign configuration in

mica-pro

.

Usage

Note:

If your project uses Lombok, place the

mica-auto

dependency after Lombok.

Maven

<code>&lt;dependency&gt;
  &lt;groupId&gt;net.dreamlu&lt;/groupId&gt;
  &lt;artifactId&gt;mica-auto&lt;/artifactId&gt;
  &lt;version&gt;${version}&lt;/version&gt;
  &lt;scope&gt;provided&lt;/scope&gt;
&lt;/dependency&gt;
</code>

Gradle ≥ 5.x

<code>annotationProcessor("net.dreamlu:mica-auto:${version}")</code>

Gradle < 5.x

<code>compileOnly "net.dreamlu:mica-auto:${version}"</code>

Diagram

Add Dependency

Dependency Build

Generated Config

Principle

Scans

@Component

annotations and automatically generates the corresponding configuration, supporting composed annotations.

License

LGPL (GNU Lesser General Public License). LGPL allows commercial software to link to the library without open‑sourcing the commercial code, but any modifications to the LGPL code itself must be released under LGPL.

User Rights

Free to use without source changes for learning, thesis, company projects, freelance work, etc.

Modifications that remain closed‑source require author permission.

When referencing, cite: mica-auto https://github.com/lets-mica/mica-auto

Javamicroservicesdependency managementSpring Bootmica-autoMica
Java Architecture Diary
Written by

Java Architecture Diary

Committed to sharing original, high‑quality technical articles; no fluff or promotional content.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.