Group: GitHub Lamspace

Sort by:Popular▼

✓Popular✓Newest

meili-orm core: annotation mapping, entity metamodel, serialization abstraction, query IR, settings projection and templated operations. Zero Spring dependencies.

meili-orm Spring Boot auto-configuration: two-level client and data wiring, index auto-initialization and settings synchronization. One jar for Boot 3.5.x and 4.x.

meili-orm Spring Boot starter aggregate: core + autoconfigure + the Boot base starter.

OpenLatch Netty 服务器（单节点与 Raft 集群形态）

Shared demo business code: fully annotated entities, passthrough settings, callbacks and REST endpoints (compiled against the Boot 3.5.16 baseline; both launcher shells reuse the same bytecode).

meili-orm repository layer: Spring Data-style declarative repositories with derived and annotated queries; all data access delegates to Operations. The only product module that depends on spring-data-commons; enabled by adding this coordinate ...

meili-orm Testcontainers integration: typed Meilisearch service container plus a Spring Boot service-connection bridge (produces MeiliConnectionDetails only). One jar for Boot 3.5.x and 4.x.

OpenLatch 客户端 SDK：异步内核 + 同步包装 + 看门狗 + 重连

OpenLatch 线路协议（.proto 定义与 protoc 生成代码）

Compatibility matrix, Boot 4.0.3 generation: starter wiring and Long-primary-key CRUD round-trips against a real server, plus version sentinels.

Optional meili-orm Jackson 3 serializer module: adding the dependency hands document serialization over to Jackson 3 in Boot 4 applications; the rest of the build keeps zero Jackson 3 compile dependencies.

OpenLatch 纯 Java 锁语义核心（无外部运行依赖）

Meilisearch Spring Boot starter: annotation-driven mapping, settings projection and templated operations (compatible with Spring Boot 3.5.x and 4.x).

Boot 3.5.16 demo launcher shell: only the application class and configuration; all business code is reused from example-common.

Boot 4.0.3 demo launcher shell: only the application class and configuration; all business code is reused from example-common (the same bytecode running on the other Boot generation).

Aggregate for the dual-generation demo: shared business code plus Boot 3.5.16 and 4.0.3 launcher shells; produces no published artifacts.

Compatibility-matrix aggregate: integration-test modules, one pinned Spring Boot generation each, compiled and run independently; produces no published artifacts.

Compatibility matrix, Boot 3.5.16 generation: starter wiring and Long-primary-key CRUD round-trips against a real server, plus version sentinels.

Compatibility matrix, Boot 4 + Jackson3 opt-in generation: verifies the "dependency equals takeover" behavior of the optional serializer module with real round-trips.

OpenLatch distributed lock: protocol, server, client SDK, Spring Boot starter and console under one roof.