| name | java-standards |
| description | Java service standards for Bitso projects. Covers tech stack requirements, project organization, code review guidelines, MapStruct usage, and build verification practices. Use when creating new Java services or reviewing existing code.
|
| compatibility | Java projects using Gradle with Spring Boot |
| metadata | {"version":"1.0.0","technology":"java","category":"standards","tags":["java","standards","code-review","project-structure","mapstruct"]} |
Java Standards
Java service standards for Bitso projects.
When to use this skill
- Creating new Java services or modules
- Understanding project organization patterns
- Reviewing Java code for standards compliance
- Configuring MapStruct for object mapping
- Verifying builds after code changes
Skill Contents
Sections
Available Resources
📚 references/ - Detailed documentation
Tech Stack
| Component | Version | Notes |
|---|
| Java | 21 (LTS) | Current LTS version |
| Gradle | 9.2.1 | Recommended for all projects |
| Spring Boot | 3.5.9 | Latest (min 3.5.9) - preparing for Spring Boot 4 |
| Database Access | jOOQ | For accessing PostgreSQL |
| Databases | PostgreSQL, Redis | Primary data stores |
| Inter-service Communication | gRPC | Standard protocol |
| Object Mapping | MapStruct | For DTO/domain mapping |
For Spring Boot upgrades, use /upgrade-to-recommended-versions.
Project Organization
Projects should be organized with domain-based modules:
root-project/
├── build.gradle
├── settings.gradle
├── docs/ # Documentation
├── bitso-libs/ # Library modules
│ ├── <subdomain>/ # Domain logic
│ └── <subdomain-proto>/ # Protobuf definitions
└── bitso-services/ # Service modules
└── <domain>/ # Spring Boot application
Build Verification
After updating Java or Groovy code, verify changes:
./gradlew test 2>&1 | grep -E "FAILED|Error" || echo "All tests passed"
./gradlew build 2>&1 | grep -E "FAILED|Error" || echo "Build successful"
If problems are found, fix them before committing.
References
Related Rules
Related Skills
