Quarkus support
Explyt Spring ships first-class Quarkus support for IntelliJ IDEA Community Edition out of the box. Despite the plugin's name, Quarkus projects are supported directly — no Spring dependency and no extra plugin required.
Quarkus support is built entirely on static code analysis. Unlike Native Context Mode for Spring, there is nothing to link and nothing to load: open a Quarkus project and the features are available immediately.
Dependency injection (CDI)
- Detect and navigate injections through
@Inject, including qualifiers and scopes. - Producers declared with
@Produceson fields and methods, with navigation in both directions — from a producer to its injection points and back. - Inspections for unsatisfied and ambiguous injection points.
Web endpoints (JAX-RS)
- JAX-RS REST resources appear in the Explyt Endpoints tool window alongside any Spring endpoints, with the same filtering and navigation. See Tool windows.
- Navigation from an endpoint entry to its handler method.
- Duplicate path detection across resources.
- Methods with an absolute URL get a Run gutter icon that opens the generated OpenAPI in Swagger UI inside the IDE — see Swagger UI client.
AOP
Interceptors and decorators are marked in the gutter, with navigation to and from the advised targets.
What is not available
The capabilities that depend on a running Spring context do not apply to Quarkus projects: the native bean model, the Spring Debugger context and transaction views, and the Spring-specific inspections.
If you hit an edge case or a construct that is not recognized, open an issue.
Further reading
See also: Tool windows · Feature overview