non-nls constants were initially present in .form files,
but became zero-tolerance warnings only after generating sources
from .form
GitOrigin-RevId: 2144db82237102cd132689a0de3ac42c0df9de5a
Introduces `JavaPluginDisposable` and migrates existing project disposables to the new project level service. #IDEA-383890 Fixed
GitOrigin-RevId: 762429b8f44959e127324d19053a8b05a818f414
cwm uses netty — packaging already fixed in another separate commit, but still we need to convert netty to simplify our build scripts
GitOrigin-RevId: a169f1203799f4fdb1adbc62c3ba2071f08325c6
Use `false` as default value for `ide.workspace.model.per.environment.model.separation` registry flag in `OptionsDirectoryProcessor` to align behavior with other usages of the flag.
GitOrigin-RevId: 61b160ef70558ed6f8953376862c20d6ff8f4b1c
The option is not universally available and is not needed when waiting for a child process via the API.
GitOrigin-RevId: fd5ae87e00cd9001d63b37a6a88f27c2de79f15e
Prevents the build toolwindow from stealing the focus when an automatic build is triggered by the automatic test runner when the code is uncompilable. #IDEA-335769 Fixed
GitOrigin-RevId: d6bd1f9fade4fab3c91b25bbe788f870aaf123bc
Stop using the local IDE runtime JDK as a fallback when the project builds remotely (Docker/SSH/WSL). This avoids launching the build with a JDK that cannot run on the target machine and prevents hard‑to‑diagnose failures. When no compatible remote JDK is found, we now fail fast. Existing local and WSL‑specific behavior remains unchanged.
GitOrigin-RevId: 3e27c308520d3522572fdfc2ee57e4d6c4e2ab63
SDK selection now accounts for the project's Eel environment rather than only WSL paths, so only SDKs runnable on the target machine are considered. When Eel is available, filtering uses compatibility checks against the project/Eel context to support generic non‑WSL remote setups. If the "wsl.use.remote.agent.for.nio.filesystem" registry key is `false`, WSL‑over‑Eel remains disabled and the legacy WslDistribution matching continues to be used.
GitOrigin-RevId: 43723999a07be66da6fc6facda079c7a70b86fc8
Routes the build system directory and project system hashing to Eel storage whenever Eel is available, and the project is non‑local, not just for WSL. This unifies remote handling so non‑local, non‑WSL projects now keep JPS-build-related files on the remote Eel side instead of the local machine.
The previous WSL‑specific logic is preserved and continues to be used for WSL projects or when Eel isn't applicable. Local projects remain in the local build system directory with no behavioral changes. This reduces cross‑machine path mismatches and keeps build state co‑located with remote sources for more reliable builds.
GitOrigin-RevId: 602fa5f5f9f2bc4649bdb37431485997d380617a
Unifies path‑mapper selection so builds work consistently for remote Eel projects in addition to WSL. When the "wsl.use.remote.agent.for.nio.filesystem" registry key is `false`, WSL‑over‑Eel is disabled, and we intentionally fall back to legacy `WslDistribution` mapping. This preserves existing local/WSL behavior while enabling remote Eel workflows.
These changes also address a likely issue in `com.intellij.compiler.server.BuildManager.scheduleBuild()` method where `currentFSChanges` previously relied on a WSL‑only mapper. It now uses the unified mapper that supports both Eel and the alternate WSL path conversion.
GitOrigin-RevId: ff5c0ad873f513c0e34b3dc01a8b79904c8e7650
The option was introduced as a Registry flag in `aba75dc4a9c7d6c33f8aa96a83d5505304e5e0b2` and later replaced with a system property in `63439ad1d476dda6f6d7640d3fb19f1dcc63917e` due to Fleet’s inability to access the Registry. The property is read but never set anywhere in the product or in `ultimate-teamcity-config`, so the behavior has effectively been disabled since 2021.1. This change removes the property handling and related code paths. No functional change is expected.
GitOrigin-RevId: a06a298f8776f3e2d648176198b30d56c1fd7021
Application‑level libraries ("Global Libraries" in UI) must be isolated by the environment, so each EEL environment sees only its own library set. This prevents cross‑environment leakage and aligns library scoping with SDK scoping.
Notes
- Environment choice is derived from the passed `Project` (carrier of the already‑resolved `EelMachine`), so selection is synchronous and safe for this API surface.
- API names stay as they are; documentation clarifies that the `Project` parameter selects the environment for the application‑level table and does not turn it into a project‑level table.
- In the Project Structure UI, the existing environment‑scoped modifiable model remains owned by the UI; outside the UI, callers get a standalone modifiable model for the chosen environment.
GitOrigin-RevId: e88445929d19012d029e79d44f09f694aba8df6f
APIs, which were marked as deprecated in 251 or earlier and don't have external usages, are marked as internal. Also, if there are no internal usages, it's also marked for removal.
GitOrigin-RevId: ffd772fc41738cdf3bcf5a122756936383184866
