This review introduces an rpc service for launching agents on workspace. There are multiple features that are not yet supported: agent session liveliness checks, ai ignores, agent's pty output, thus this ability is hidden by a feature flag and can only be enabled for the agent mode.
Merge-request: FLEET-MR-6342
Merged-by: Fedor Bocharov <Fedor.Bocharov@jetbrains.com>
GitOrigin-RevId: 545436c7f894f99bcff68285db4acc483ae303c6
Now a module-descriptors.dat file is generated alongside module-descriptors.jar, and it's used to load the module descriptors at runtime. The new file contains the same data as module-descriptors.jar, but it's stored in binary format instead of XML files inside a ZIP file. This reduced the time required to load the data up to 10 times.
GitOrigin-RevId: 7b8e5e13e27f13db8ee252001784c7126527b4ea
Now a module-descriptors.dat file is generated alongside module-descriptors.jar, and it's used to load the module descriptors at runtime. The new file contains the same data as module-descriptors.jar, but it's stored in binary format instead of XML files inside a ZIP file. This reduced the time required to load the data up to 10 times.
GitOrigin-RevId: 9139d637b12bc01085d7dcf03a273ad8779b9d49
In Fleet, `scope=PROVIDED` would mean potentially two things:
A. either, the module was required only in compile classpaths
B. or, Fleet runtime will provide that module at runtime
B is not true anymore, inter-plugin dependencies are mandatory and explicit in the `build.gradle.kts` of the Fleet plugin, using the SDK DSL.
All these scopes were leftovers from the time the tooling was using them to implicitly resolve inter-plugin dependencies.
If some scope were there for A, they will be re-introduced, but we believe nobody were using them for that value.
`fleet.util.multiplaform` or compiler plugins are such case of A and are left as PROVIDED.
(cherry picked from commit eeed5aebe8f9e13df7eb15e83ba582390b2d98eb)
FLEET-MR-6307
GitOrigin-RevId: c305f1d29711688de62598606a899fca35f97837
In Fleet, `scope=PROVIDED` would mean potentially two things:
A. either, the module was required only in compile classpaths
B. or, Fleet runtime will provide that module at runtime
B is not true anymore, inter-plugin dependencies are mandatory and explicit in the `build.gradle.kts` of the Fleet plugin, using the SDK DSL.
All these scopes were leftovers from the time the tooling was using them to implicitly resolve inter-plugin dependencies.
If some scope were there for A, they will be re-introduced, but we believe nobody were using them for that value.
(cherry picked from commit 69eadc4e141567da97944474ab68c688bec221c7)
FLEET-MR-6307
GitOrigin-RevId: ec668fb8526ac7ac2065a4495e3ab605dae94159
A new content module 'intellij.libraries.ai.grazie.spell.gec.engine.local' is introduced. It includes 'ai.grazie.spell.gec.engine.local' library and related libraries which needs to be loaded by the same classloader. This is needed to avoid bundling these libraries in several plugins after 'intellij.spellchecker' was converted to a content module and the libraries were removed from the main classloader of the core plugin.
Duplicating artifacts are removed from intellij.grazie.core and intellij.spellchecker modules.
GitOrigin-RevId: 85cff18e75062a659cc97790fb4a55d9109308e9
Related change in pty4j: 4f7222273a
Bundled ConPTY was updated to Windows Terminal (v1.21.2701.0).
https://github.com/microsoft/terminal/releases/tag/v1.21.2701.0
This makes behavior of IDE built-in terminal closer to the behavior of Windows Terminal.
GitOrigin-RevId: e06b28c129d30fca2a4783cc0d2a7739fdfa5d57
