Repository navigation
Feature Request: Add Support for Java/Kotlin, Spring Boot, and Maven Environment Workflows #147
Description
Hi! Love what rtk does for CLI efficiency and token savings in AI-assisted development. As more teams adopt AI coding agents for Java and Kotlin (especially with Spring Boot and Maven), it would be incredibly valuable to extend rtk’s optimization capabilities to common workflows in these ecosystems.
Currently, rtk supports tools like cargo, npm, docker, and git, but Java/Kotlin developers using mvn, spring-boot:run, or environment-heavy setups (e.g., application.properties, profile-specific configs) don’t benefit as much.
Suggested Enhancements:
Maven Command Optimization
Support for rtk mvn clean install with condensed output (e.g., hide repetitive INFO logs, summarize test results).
Filter noisy Maven logging while preserving critical errors/warnings.
Spring Boot Dev Experience
Smart parsing of Spring Boot startup logs:
Highlight key info (active profiles, port, endpoints) while collapsing bean creation logs.
Detect and summarize common issues (e.g., Port already in use, NoSuchBeanDefinitionException).
Environment & Configuration Awareness
Add rtk env or rtk print-env to safely display filtered environment variables (with secrets redacted).
Support for .env files and Spring application-{profile}.yml previews with token-efficient summaries.
Integration with IDE/AI Agents
Auto-detect pom.xml or build.gradle.kts and suggest relevant rtk commands.
Compact output for mvn dependency:tree (similar to rtk deps for Rust/Node).
Test Output Filtering
For mvn test or ./gradlew test: show only failed/skipped tests (like rtk test cargo does).
This would make rtk a truly universal tool for AI-assisted development across JVM and non-JVM projects.
Thanks for considering!
— A fan of efficient coding 🙌
Reacted by Art Shendrik, Daniel Dudziak and Reginaldo L. Russinholi
Reacted by Yonatan Karp-Rudin and Devon Hillard
Reacted by Art Shendrik and Sebastien
Activity
art-shen commentedon Feb 16, 2026
Yes, please! For gradle it would be so huge
pszymkowiak commentedon Feb 17, 2026
Thanks for the detailed request! JVM support makes sense as a future addition.
The most impactful starting points would be:
The Spring Boot log parsing and env/config features are interesting but lower priority — they're more specialized.
PRs welcome — start with mvn test filtering as a first step. See src/cargo_cmd.rs or src/pytest_cmd.rs for the test filtering pattern to follow.
art-shen commentedon Feb 18, 2026
I think Gradle is currently even more common in JVM / Android / KMP projects, comparing to maven.
E.g.,:
alkaphreak commentedon Feb 18, 2026
As a senior Java/Kotlin consultant i used Gradle only one time, every other time it was Maven.
And for the framework part, almost exclusively Spring / Spring Boot.
yonatankarp commentedon Feb 21, 2026
As a JVM developer in over 10 years I used Maven only once and still regretting it - I would love to have Gradle support ❤️
feat: add Maven (mvn) command support with build, test, and dependenc…
feat: add 5 new TOML built-in filters (ollama, nx, gradle, spring-boo…
pszymkowiak commentedon Mar 16, 2026
Fixed in v0.30.0 — TOML filters exist for gradle, mvn-build, spring-boot. Tested locally:
rtk mvn clean installcorrectly strips plugin headers and keeps build results.alkaphreak commentedon Mar 16, 2026
Awesome. I will try it soon.
feat: add 5 new TOML filters (ollama, nx, gradle, spring-boot, jira) (#…
Release v0.31.0 — develop → master (#666)
feat: add 5 new TOML filters (ollama, nx, gradle, spring-boot, jira) (#…
feat: add 5 new TOML filters (ollama, nx, gradle, spring-boot, jira) (#…
Release v0.31.0 — develop → master (rtk-ai#666)
Release v0.31.0 — develop → master (rtk-ai#666)
feat: add 5 new TOML filters (ollama, nx, gradle, spring-boot, jira) (r…