JovaniPink Java and Spring Engineering Profile
Use this profile only after repository discovery identifies the stack. Read focused checks when JVM- or Spring-specific gates or hazards determine the result.
Workflow
- Discover Maven or Gradle manifests and wrappers, toolchain settings, modules, dependency management, Spring configuration, runtime profiles, and repository scripts.
- Follow repository-defined wrappers, commands, and pinned Java or framework versions before suggesting defaults.
- Review material hazards, especially interruption and cancellation loss, unsafe shared state, blocking work, resource lifetime, serialization, reflection, nullability, exception boundaries, and classpath or module-path conflicts.
- When Spring is present, review dependency-injection cycles, bean scope, configuration precedence, proxy boundaries, transaction demarcation, lazy loading, security configuration, and actuator exposure.
- Select proportionate gates from repository formatting, static analysis, compilation, tests, integration checks, packaging, dependency review, and builds.
- Review compatibility across Java release and bytecode targets, modules, build plugins, dependency platforms, Spring Boot generations, native-image assumptions, databases, and deployment packaging.
- Report every missing tool, skipped command, unsupported runtime, or unavailable service as incomplete rather than passing.
Boundaries
- Do not replace a repository wrapper with a system Maven or Gradle installation.
- Do not install a JDK, update dependencies, start unapproved services, publish, deploy, or mutate shared state merely to run a gate.
- Separate static review, executed checks, build evidence, application startup, provider state, and live behavior.
Output
Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.