262.35.123

[imuromtsev]

This release is the last one for IntelliJ IDEA 2024.2 and 2024.3. Later releases support IntelliJ IDEA 2025.1 and newer.

Bean model that matches the running application

• Bean conditions follow Spring Boot: @ConditionalOnProperty (also repeated, matchIfMissing, ${VAR:default}), @ConditionalOnBooleanProperty, composed conditions and conditions on library classes are evaluated as Boot evaluates them ([BUG] Static bean model keeps library beans of absent stacks and hides beans a condition turns off #496, Merged composed-annotation values for the callers that still read declared values #672, [BUG] @ConditionalOnProperty on a compiled library class is undecided: "property name cannot be resolved" #759)
• Web conditions follow Boot's web application type: servlet, reactive and client-only applications are told apart, and spring.main.web-application-type is honoured ([BUG] Static bean model keeps library beans of absent stacks and hides beans a condition turns off #496)
• Profiles work as in Spring: @Profile values are alternatives, constants are read by value, and spring.profiles.group activates its member profiles (Static bean model treats @Profile array values as AND instead of OR #548, @Profile with an unresolvable constant hides the bean #562, [BUG] Static bean model ignores spring.profiles.group, so a @Profile bean activated through a group is reported as absent #529)
• Beans that a profile turns off stay visible as inactive beans with their reason, in Search Everywhere and in the MCP bean tools (MCP bean lookup: list @Profile-inactive beans and tune the inactive sample for small budgets #634)
• Library @Controller and @Service classes are beans only when a component scan covers them (Static bean model lists library @Controller classes as beans next to their auto-configuration factory #645)
• A class registered by @Import or @EnableConfigurationProperties follows the conditions of the configuration that registers it; a plain @ConfigurationProperties class is a bean only when @EnableConfigurationProperties or @ConfigurationPropertiesScan registers it, and a component also listed in @EnableConfigurationProperties is two beans, as in Spring ([BUG] Static bean model keeps library beans of absent stacks and hides beans a condition turns off #496, A @ConfigurationProperties class in the scanned packages is a bean without @ConfigurationPropertiesScan #741, [BUG] A component also listed in @EnableConfigurationProperties is two beans in Spring but one in the static and native models #782)
• Bean names follow Spring's generator: URLService and ABTestController keep their names, nested classes are named outer.Inner, and beans registered by @Import or @EnableConfigurationProperties get the fully qualified names Spring gives them ([BUG] Static bean model lowercases default bean names that Spring keeps (XFoo, URLService) and ignores nested-class names #758, [BUG] Static model names beans from @Import, @EnableConfigurationProperties and AutoConfiguration.imports by the scan default instead of Spring's fully-qualified names #781)
• @Bean(name = …), composed @Bean annotations and covariant @Bean overrides give the bean name and type Spring gives ([BUG] Static bean model: an overridden @Bean is a second bean, a named @Bean keeps its method name, abstract classes are listed #506, Composed @Bean annotation with @AliasFor(annotation = Bean.class, attribute = "name") is not read for the bean name #592, Covariant @Bean override without @Bean is typed by the superclass factory method #594, Bean readers outside the model still type a covariant @Bean override by the superclass method #680)
• A component scan declared in a dependency module, a default-package application and an @EnableAutoConfiguration application now give the correct beans, and an application in test sources no longer widens the beans of production code ([BUG] Static bean model drops the components a dependency module's @ComponentScan adds, and reports the miss as COMPLETE #495, [BUG] Default-package application hides scanned components in the static bean model #710, [BUG] An application declared with @EnableAutoConfiguration instead of @SpringBootApplication is not detected, and test-source applications are listed unmarked #532, [BUG] Static bean model admits beans through the scan roots of a test-source application #772)
• Starters that are only on the application's runtime classpath, such as runtimeOnly dependencies, contribute their beans, so injecting them no longer reports "No beans" ([BUG] Static bean model reads library beans from the compile classpath, so a runtime-only starter bean is a confident NO_CANDIDATE #780)
• MyBatis mappers (@MapperScan, @Mapper) and Spring Integration @MessagingGateway interfaces are beans (Interfaces registered by non-component-scan registrars (Spring Integration @MessagingGateway, MyBatis mappers) are not modelled as beans #598)
• Injection points with type arguments find beans whose arguments come from a supertype, such as a @Bean TestGenericV1 for TestGeneric<String>, also inside List, Optional, ObjectProvider and Map, in bean gutters, the autowiring inspection and explyt_find_spring_bean ([BUG] Bean navigation. Autowired not worked for generic filed if bean created from method #799)

New inspections and quick fixes

• Bean name collisions that fail startup: two @Bean methods with the same bean name on Spring Framework 6.2 and later, and a @Bean method overridden across two registered configurations (Inspection: two @Bean methods with the same bean name in one configuration class fail Spring Boot startup #597, Duplicate @Bean name inspection: inherited collisions, overriding property scope, rename fix #668, Duplicate @Bean name inspection is silent on Spring 7 when bean definition overriding is allowed #686, Duplicate @Bean name inspection reports a startup failure on Spring Framework before 6.2.0 #689, Duplicate @Bean name inspection is silent when overriding is allowed but Spring silently drops one method #698, Duplicate @Bean name inspection misses a factory method overridden by a registered configuration subclass #714)
• A composed @Bean name that conflicts with its meta-annotation and fails startup on Spring Framework 6 (Inspection: Spring 6 composed @Bean with a convention name attribute and a meta @Bean name fails at startup #632)
• A stereotype annotation on an abstract class that Spring does not register, with a quick fix (Inspection: @Component on an abstract class has no effect #601)
• A @Controller or @RestController value that looks like a request path, with a quick fix that moves it to @RequestMapping ([FEATURE] Inspection: a stereotype value that looks like a request path, e.g. @RestController("/app") #534)
• An Actuator endpoint extended by more than one @EndpointWebExtension, which fails startup ([BUG] Actuator web extensions: duplicate extensions, consumes in the operation key, library extensions, extension conditions #655)
• Spring Boot 3.4 and 3.5 @MockBean and @SpyBean deprecation, with a quick fix to @MockitoBean and @MockitoSpyBean
• Spring Boot 3 management.endpoint.httptrace.* keys, with a quick fix to httpexchanges
• An enum configuration value or a hint value that is not in Spring's recommended spelling, with a quick fix
• Fewer false errors: bean-name checks in @Lookup, @DependsOn, cache annotations and @WithUserDetails skip classes that Spring does not register ([BUG] @Lookup inspection reports "Cannot resolve bean" on a class that is not a bean #783)

Endpoints and HTTP

• Spring Explyt installs in IDEs without the JCEF module (e.g. Android Studio); the OpenAPI preview, its "Run in Swagger" and "Open in UI" gutters, and Spring Initializr wizard are available only where JCEF is present ([COMPATIBILITY] Plugin cannot be installed in IDEs without com.intellij.modules.jcef (Android Studio) #817)
• The Endpoints tool window lists the built-in Actuator endpoints (health, info, metrics and others) next to project endpoints, with exposure and access as Boot reads them ([BUG] Built-in Actuator endpoints are missing from the endpoint model, the Endpoints tool window and the MCP endpoint tools #476, [BUG] Actuator controller endpoints get httpMethods ACTUATOR and no handler; operation produces, access and @Selector are not read #512, [FEATURE] Show Actuator endpoints in the Explyt Endpoints tool window #315)
• Find an endpoint from a URL that you paste from a browser, a log or a curl command ([FEATURE] Find an endpoint from a pasted URL in the Endpoints tool window, and resolve absolute URLs in string-URL references #453)
• Functional routes: router { }, WebMvc.fn, Java RouterFunctions builders, nested path() and nest() prefixes and verb predicates are listed as Spring serves them ([BUG] router { } and WebMvc.fn functional routes are not discovered as endpoints #415, [BUG] Java functional-router builder nest/path callbacks are not traversed by the endpoint loader #580, Router DSL: RequestPredicates.path("/a").nest { } adds no prefix #606, Router model leftovers after #606 #627)
• Request mappings declared on an implemented interface or a superclass, composed mapping annotations and property placeholders in paths are resolved, and a path taken from a constant updates when you edit the constant ([BUG] An endpoint mapped on an implemented interface is modelled at the interface method instead of the controller's override #533, MetaAnnotationsHolder ignores @AliasFor attribute defaults and convention overrides of composed annotations #651, Merged composed-annotation values for the callers that still read declared values #672, [BUG] Endpoint paths keep property placeholders verbatim, and a declared server.servlet.context-path is never read #451)
• "Run in Swagger" and the HTTP client use the context path, servlet path and server port that the application declares, also through nested placeholders ([BUG] Endpoint paths keep property placeholders verbatim, and a declared server.servlet.context-path is never read #451, [BUG] Swagger UI / .http server URL from a nested server.port placeholder is truncated and unresolved #779)
• MockMvc, WebTestClient and RestClient requests in tests are found as endpoint usages, also for URLs built from templates and URI builders ([BUG] explyt_find_spring_endpoint exposes the coroutine continuation of a suspend handler; testUrlReferences misses string-template and absolute URLs #463, [BUG] Test URL usages: the localhost-only host policy filters in-process MockMvc requests, java.net.http to localhost is not read, and MockMvc lines are reported twice #467, [BUG] WebFlux controllers are typed Spring MVC, and a WebTestClient URI builder lambda is not an endpoint usage #497)
• OpenAPI 3.2 support, refreshed OpenAPI 3.0 and 3.1 schemas, Swagger UI 5.32.15 and a working OAuth2 Authorize flow in the preview
• "Generate OpenApi Doc" adds missing operations and keeps the documented ones (Generate OpenApi Doc on a @RequestMapping without method wipes the documented path #640, Generate OpenApi Doc reads YAML specs twice and never targets a JSON spec #641, [BUG] Routes that answer any HTTP method get an empty OpenAPI path item and no "Add to OpenAPI" action #662)

Configuration properties

• Navigation works through list indexes, map keys in bracket notation and constructor-bound properties ([BUG] No navigation from map-entry keys under a bracket-notation map key containing dots #383, [BUG] No navigation to map/list element members declared as Kotlin val or Java record components #384, [BUG] No navigation from list-element keys nested under a map entry #396, [BUG] No navigation from keys more than one level below a collection index #471)
• Enum values are accepted and completed in any relaxed spelling (request-headers for REQUEST_HEADERS)
• Fewer false errors: keys used in any Spring annotation placeholder, in several files or from a test module are resolved ([BUG] Property which has usage in @ConditionalOnProperty marked as not resolved in properties config #118, [BUG] False positive 'Cannot resolve key property' for keys consumed only via @KafkaListener or other non-@Value Spring annotations #380, [BUG] 'Cannot resolve key property' in main application.yaml when the only usage is a @Value in test sources #381, [BUG] ConditionalOnBooleanProperty keys lack property references and completion #570)
• logging.level.<name> navigates to the logger package or class and to logging groups
• The spellchecker no longer flags Spring's declared key segments ([FEATURE] Suppress typo inspections for valid configuration keys #363)

Events

• Navigate from a listener to events that Spring and libraries publish, such as ApplicationReadyEvent and AuthenticationSuccessEvent ([BUG] Event publisher gutter reports no publisher for container-published lifecycle events #426, [BUG] Event listener gutter on a library publishEvent call always finds nothing: module is null for library PSI #427, [BUG] Event publisher gutter finds nothing for library-published events outside the two lifecycle bases #431)

Native Context Mode

• Link a Gradle bootRun run configuration ([BUG] A Gradle bootRun configuration cannot be linked, so its env and profiles are lost #376)
• Sync failures name the class that is missing, and broken project links heal themselves
• A sync started before the module has a JDK, for example while the build is still being imported, fails at once with a message naming the module instead of an IDE error and a stalled sync

MCP tools for AI agents

• New explyt_find_spring_bean tells an agent which bean Spring injects at a field or a constructor parameter
• Endpoint contracts describe the JSON that Jackson writes: polymorphic types, Spring Data Page, HATEOAS models, naming strategies and enums ([BUG] Endpoint contract describes Page<T> and HATEOAS models by their payload, not their wire shape #557, Endpoint contract: page wire shape gaps after the Page/Slice support #639)
• explyt_trace_spring_call_chain shows the tests that a change breaks and the @Transactional and @Async advice around each method ([BUG] explyt_trace_spring_call_chain misses interface- and URL-based test references and has no size budget or per-node proxy annotations #452)
• All tools page their answers within a character budget, with a page revision that stays stable while you edit unrelated files, and report built-in Actuator endpoints with exposure and access (Endpoint MCP tools have no character budget #635)

Performance and stability

• Fewer UI freezes when a project opens, when a run configuration is selected and on the first action after startup (Freeze #294, Freeze: Sentry initialization runs on the EDT while recording an action breadcrumb #307)
• Faster highlighting of application.yaml and .properties files
• Gradle gradlew and mvnw are executable in projects generated through Spring Initializr ([FEATURE] Make gradlew executable after project creation through Spring Initializr #60)
• Compatible with IntelliJ IDEA 2026.3: endpoint actions and the configuration metadata intention no longer depend on classes that 2026.3 removes

---

This discussion was created from the release 262.35.123.