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 🙌