Also, `MissingJavadocInspection` is now enabled by default.
(cherry picked from commit 153ae8c588cba01c7444cb0eb59df2a8d525cd27)
IJ-CR-209257
GitOrigin-RevId: f913c5093788926ee3edbf81fab7571daaf0eb16
RDCT test framework uses Java debugger implementation classes from host/backend-side helpers, so the JPS test dependency must stay on the compile classpath.
Do not generate that dependency into the shared RDCT test plugin descriptor loaded by JetBrains Client. The backend-only Java debugger module is not resolvable in frontend mode and excludes the RDCT test plugin chain during startup.
IJ-MR-184958 IJ-MR-184993 IJ-MR-179029 IJ-MR-184126 IJ-MR-181153 IJ-MR-146078 IJ-MR-175479 IJ-MR-186058 IJ-MR-193195 IJ-MR-196957 IJ-MR-199124 IJ-MR-197441 IJ-MR-204135 IJ-MR-204674 IJ-MR-205883
GitOrigin-RevId: 7ff5463cd43d6b6c4cc6b9363370def9d4c68dcf
The Kotlin standalone LSP bundle declares feature modules that depend on intellij.kotlin.base.resources and intellij.kotlin.codeInsight.shared. In the analyzer bundle these modules are represented by synthetic descriptors rather than the full IDE plugin descriptors, so expose them as empty modules on the synthetic Kotlin plugin.
This keeps the plugin dependency graph satisfiable without pulling in the full intellij.kotlin.codeInsight.shared descriptor and its IDE-only dependencies, which allows the Kotlin LSP feature plugin to load during standalone diagnostics tests.
IJ-MR-184958 IJ-MR-184993 IJ-MR-179029 IJ-MR-184126 IJ-MR-181153 IJ-MR-146078 IJ-MR-175479 IJ-MR-186058 IJ-MR-193195 IJ-MR-196957 IJ-MR-199124 IJ-MR-197441 IJ-MR-204135 IJ-MR-204674 IJ-MR-205883
GitOrigin-RevId: 8b76af0c4dc903e6e674765a4c3f5ef92d6b76c1
Java backend no longer depends on Java execution implementation, so registering execution and test-discovery extensions from the backend descriptor makes split-mode plugin classloaders fail to create those extensions. Register them from the Java execution implementation module instead, and keep the related platform registrations in their owning descriptors.
Also add the missing Test Runner wrapper plugin to REST client env tests so test-runtime plugin resolution includes the extension points required by REST client request execution.
IJ-MR-184958 IJ-MR-184993 IJ-MR-179029 IJ-MR-184126 IJ-MR-181153 IJ-MR-146078 IJ-MR-175479 IJ-MR-186058 IJ-MR-193195 IJ-MR-196957 IJ-MR-199124 IJ-MR-197441 IJ-MR-204135 IJ-MR-204674 IJ-MR-205883
GitOrigin-RevId: 53920289ed61755459a1ebc4d84df1cb5b1a05c1
Keep java.impl free from XML implementation dependencies by moving Java DOM converters, XML completion/reference helpers, and related UI/action registrations into the new Java XML DOM implementation module.
Downstream modules that directly use those converters now depend on intellij.java.xml.dom.impl explicitly, while java.impl uses platform-neutral file type and HTML utilities where it only needs generic XML/HTML behavior.
IJ-MR-184958 IJ-MR-184993 IJ-MR-179029 IJ-MR-184126 IJ-MR-181153 IJ-MR-146078 IJ-MR-175479 IJ-MR-186058 IJ-MR-193195 IJ-MR-196957 IJ-MR-199124 IJ-MR-197441 IJ-MR-204135 IJ-MR-204674 IJ-MR-205883
GitOrigin-RevId: 07d6d3b90c1f0a89ed5d12e517e05d011d6f6f7e
Java-specific ConverterManager override must be registered after the XML DOM implementation service is available. Keeping that override in the broad Java implementation descriptor allows pluginized test runs to load Java before the DOM service and fail during application startup.
Move the override class into a dedicated Java XML DOM content module and wire that module into the Java plugin backend content. The module keeps the real JPS/Bazel dependency on intellij.xml.dom.impl; Product DSL generation leaves the embedded XML DOM runtime dependency implicit while preserving the build-time dependency edge.
IJ-MR-184958 IJ-MR-184993 IJ-MR-179029 IJ-MR-184126 IJ-MR-181153 IJ-MR-146078 IJ-MR-175479 IJ-MR-186058 IJ-MR-193195 IJ-MR-196957 IJ-MR-199124 IJ-MR-197441 IJ-MR-204135 IJ-MR-204674 IJ-MR-205883
GitOrigin-RevId: 3bca5bbbed58bb2a09db8408f460c887173daf9e
Language Server products intentionally do not include the platform bookmarks plugin. After bookmarks were pluginized, Java and VCS Log still had direct dependencies on bookmark implementation modules, which could exclude Java Core during plugin set resolution.
Move the Java package and VCS Log bookmark providers into optional content modules loaded only with the relevant plugins, while keeping a small VCS Log support extension point in the core module. This preserves bookmark behavior when the bookmarks plugin is present without forcing bookmarks into products that exclude it.
IJ-MR-184958 IJ-MR-184993 IJ-MR-179029 IJ-MR-184126 IJ-MR-181153 IJ-MR-146078 IJ-MR-175479 IJ-MR-186058 IJ-MR-193195 IJ-MR-196957 IJ-MR-199124 IJ-MR-197441 IJ-MR-204135 IJ-MR-204674
GitOrigin-RevId: f6bad861b518b5a6cdbaeed0e133c94041821b6d
The platform uses them only for migrating settings if the implementation inherits from AbstractUrlFavoriteConverter, so other implementations actually aren't used.
GitOrigin-RevId: 63e191fe785f3ee6e48bddd6fa788fc4df23c811
Registering settings in XML module descriptors makes them easily discoverable, especially when PersistentStateComponents are light services. Currently, this registration is used for settings sync in remote development.
GitOrigin-RevId: 9d5198e0a840ee368e87eee319c5e360c97651a8
plugin.xml class-name completion in XML depends on XmlBasicToClassNameDelegator running before JavaClassReferenceCompletionContributor. The latter stops the remaining chain after package-only reference completion, so plugin.xml class attributes lose inner-class and long-name completion if it comes before XmlBasicToClassNameDelegator.
GitOrigin-RevId: 53887d7ad913a48003271745bc3d509fc2f0604d
