This is needed for consistency with the naming scheme: the parts used inside a separate frontend process only should be named '*.frontend.split'.
GitOrigin-RevId: e6b8489f4ec7337f5e1186590d2814c4a446d77f
explicit deps 2
explicit deps
update test expectations
continue packaging extracted 'dep-graph' module into the jps-builders.jar
temporarily comment test
add extracted intellij.platform.jps.build.dependencyGraph module to jps artifacts
exclude intellij.tools.build.bazel.jvmIncBuilder module and patched kotlinc from the list of modules; used in bazel build only
cleanup comments
add dependency on the newly extracted dep-graph module
suppress auto generation
add kotlin facet
correct idea module name
add compiler plugin deps
Merge remote-tracking branch 'origin/jeka/bazel-inc-builder' into jeka/bazel-inc-builder
KTIJ-34048 Add support for Kotlin compiler plugins in Bazel
Introduce plugin configuration for the incremental Kotlin compiler, enabling support for plugins like kotlinx-serialization and Compose. Added methods to manage plugin classpaths and integrate them into the compiler configuration. This improves extensibility for Kotlin builds in Bazel.
exclude 'patched-kotlin-compiler-for-bazel' from checks
use language level consistent with jps classes
sync community and ultimate module list
KTIJ-34048 Implement directory traversal in KotlinVirtualFileProvider
Replaced the placeholder logic in `findVfsChildren` with actual directory traversal using `OutputSink#list`. Introduced a new `list` method in `OutputExplorer` and its implementation in `OutputSinkImpl` to support this functionality (without directory filtering)
Merge remote-tracking branch 'origin/jeka/bazel-inc-builder' into jeka/bazel-inc-builder
allow no sources for 'patched-kotlin-compiler-for-bazel' and 'qdox' libraries
KTIJ-34048 Add Kotlin-based virtual file handling for incremental builds
Introduce `KotlinVirtualFileProvider` and related utilities like `OutputFileSystem` and `OutputVirtualFile` to support virtual file interactions. Updated `KotlinCompilerRunner` to integrate the virtual file system with the Kotlin compiler configuration.
allow unused 'patched-kotlin-compiler-for-bazel'
fix missing module registrations
recovering from merge conflicts
restore from merge leftover
depend on patched kotlinc via 'provided' dependency
Merge remote-tracking branch 'origin/jeka/bazel-inc-builder' into jeka/bazel-inc-builder
# Conflicts:
# community/build/jvm-rules/jvm-inc-builder/intellij.tools.build.bazel.jvmIncBuilder.iml
# community/platform/build-scripts/bazel/src/org/jetbrains/intellij/build/bazel/BazelBuildFileGenerator.kt
fix package name for the extracted 'dependencyGraph' module
rename inc-builder module according to naming conventions
split api dumps for extracted modules
inspection fix
inspection fix
KTIJ-34048 Rename pipeline.kt to kotlinPipeline.kt for clarity
The file rename reflects its specific purpose related to Kotlin. This improves code readability and aligns with naming conventions.
KTIJ-34048 Add support for Kotlin compiler configuration updates
Introduce a configuration updater in BazelJvmCliPipeline to enable dynamic updates to the Kotlin compiler configuration. This includes a new pipeline phase, `BazelConfigurationUpdaterPipelinePhase`, ensuring configurations can be modified during the compilation process.
KTIJ-34048 Don't use GeneratedJvmClass because it depends on filesystem
Replaced GeneratedJvmClass with KotlinJvmGeneratedFile for .class outputs to improve handling and clarity. Introduced KotlinJvmGeneratedFile as a new class to encapsulate relevant logic, ensuring better separation of concerns and metadata processing. Updated related bytecode handling to use this new implementation.
KTIJ-34048 Add message collector support
KTIJ-34048 Implement Kotlin compiler pipeline for Bazel integration
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
jps-to-bazel: support shared modules in bazel generator
extract bazel inc builder and dep graph into separate modules
KTIJ-34048 Rename pipeline.kt to kotlinPipeline.kt for clarity
The file rename reflects its specific purpose related to Kotlin. This improves code readability and aligns with naming conventions.
KTIJ-34048 Add support for Kotlin compiler configuration updates
Introduce a configuration updater in BazelJvmCliPipeline to enable dynamic updates to the Kotlin compiler configuration. This includes a new pipeline phase, `BazelConfigurationUpdaterPipelinePhase`, ensuring configurations can be modified during the compilation process.
KTIJ-34048 Don't use GeneratedJvmClass because it depends on filesystem
Replaced GeneratedJvmClass with KotlinJvmGeneratedFile for .class outputs to improve handling and clarity. Introduced KotlinJvmGeneratedFile as a new class to encapsulate relevant logic, ensuring better separation of concerns and metadata processing. Updated related bytecode handling to use this new implementation.
KTIJ-34048 Add message collector support
KTIJ-34048 Add tracker processing for Kotlin compiler runner in Bazel
Enhanced the KotlinCompilerRunner to process generated files and extract data such as inline constants, enum-when expressions, imports, and lookup usages. Introduced processing methods for these trackers and ensured proper initialization for robust build services.
KTIJ-34048 Implement Kotlin compiler pipeline for Bazel integration
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
extract bazel inc builder and dep graph into separate modules
less dependencies on platform modules
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
extract bazel inc builder and dep graph into separate modules
add dependency to patched kotlic
Add patched Kotlin compiler for Bazel
KTIJ-34048 Rename pipeline.kt to kotlinPipeline.kt for clarity
The file rename reflects its specific purpose related to Kotlin. This improves code readability and aligns with naming conventions.
KTIJ-34048 Add support for Kotlin compiler configuration updates
Introduce a configuration updater in BazelJvmCliPipeline to enable dynamic updates to the Kotlin compiler configuration. This includes a new pipeline phase, `BazelConfigurationUpdaterPipelinePhase`, ensuring configurations can be modified during the compilation process.
KTIJ-34048 Don't use GeneratedJvmClass because it depends on filesystem
Replaced GeneratedJvmClass with KotlinJvmGeneratedFile for .class outputs to improve handling and clarity. Introduced KotlinJvmGeneratedFile as a new class to encapsulate relevant logic, ensuring better separation of concerns and metadata processing. Updated related bytecode handling to use this new implementation.
KTIJ-34048 Add message collector support
KTIJ-34048 Implement Kotlin compiler pipeline for Bazel integration
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
extract bazel inc builder and dep graph into separate modules
KTIJ-34048 cleanups and refactorings, TODOs added
KTIJ-34048 Rename pipeline.kt to kotlinPipeline.kt for clarity
The file rename reflects its specific purpose related to Kotlin. This improves code readability and aligns with naming conventions.
KTIJ-34048 Add support for Kotlin compiler configuration updates
Introduce a configuration updater in BazelJvmCliPipeline to enable dynamic updates to the Kotlin compiler configuration. This includes a new pipeline phase, `BazelConfigurationUpdaterPipelinePhase`, ensuring configurations can be modified during the compilation process.
KTIJ-34048 Don't use GeneratedJvmClass because it depends on filesystem
Replaced GeneratedJvmClass with KotlinJvmGeneratedFile for .class outputs to improve handling and clarity. Introduced KotlinJvmGeneratedFile as a new class to encapsulate relevant logic, ensuring better separation of concerns and metadata processing. Updated related bytecode handling to use this new implementation.
KTIJ-34048 Add message collector support
KTIJ-34048 Add Kotlin compiler arguments processing
KTIJ-34048 Add tracker processing for Kotlin compiler runner in Bazel
Enhanced the KotlinCompilerRunner to process generated files and extract data such as inline constants, enum-when expressions, imports, and lookup usages. Introduced processing methods for these trackers and ensured proper initialization for robust build services.
KTIJ-34048 Implement Kotlin compiler pipeline for Bazel integration
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
extract bazel inc builder and dep graph into separate modules
jps-builders-6 moved
less dependencies on platform modules
rules_jvm: dummy BUILD.bazel for dependency-graph and jvm-inc-builder
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
extract bazel inc builder and dep graph into separate modules
fix package name for the extracted 'dependencyGraph' module
rename inc-builder module according to naming conventions
split api dumps for extracted modules
inspection fix
inspection fix
merge leftover: fix missing module 2
merge leftover: fix missing module
Merge remote-tracking branch 'origin/jeka/bazel-inc-builder' into jeka/bazel-inc-builder
# Conflicts:
# community/build/jvm-rules/jps-builders-6/BUILD.bazel
# community/build/jvm-rules/jvm-inc-builder/BUILD.bazel
add dependency to patched kotlic
Add patched Kotlin compiler for Bazel
KTIJ-34048 Rename pipeline.kt to kotlinPipeline.kt for clarity
The file rename reflects its specific purpose related to Kotlin. This improves code readability and aligns with naming conventions.
KTIJ-34048 Add support for Kotlin compiler configuration updates
Introduce a configuration updater in BazelJvmCliPipeline to enable dynamic updates to the Kotlin compiler configuration. This includes a new pipeline phase, `BazelConfigurationUpdaterPipelinePhase`, ensuring configurations can be modified during the compilation process.
KTIJ-34048 Don't use GeneratedJvmClass because it depends on filesystem
Replaced GeneratedJvmClass with KotlinJvmGeneratedFile for .class outputs to improve handling and clarity. Introduced KotlinJvmGeneratedFile as a new class to encapsulate relevant logic, ensuring better separation of concerns and metadata processing. Updated related bytecode handling to use this new implementation.
KTIJ-34048 Add message collector support
KTIJ-34048 Implement Kotlin compiler pipeline for Bazel integration
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
extract bazel inc builder and dep graph into separate modules
KTIJ-34048 cleanups and refactorings, TODOs added
KTIJ-34048 Rename pipeline.kt to kotlinPipeline.kt for clarity
The file rename reflects its specific purpose related to Kotlin. This improves code readability and aligns with naming conventions.
KTIJ-34048 Add support for Kotlin compiler configuration updates
Introduce a configuration updater in BazelJvmCliPipeline to enable dynamic updates to the Kotlin compiler configuration. This includes a new pipeline phase, `BazelConfigurationUpdaterPipelinePhase`, ensuring configurations can be modified during the compilation process.
KTIJ-34048 Don't use GeneratedJvmClass because it depends on filesystem
Replaced GeneratedJvmClass with KotlinJvmGeneratedFile for .class outputs to improve handling and clarity. Introduced KotlinJvmGeneratedFile as a new class to encapsulate relevant logic, ensuring better separation of concerns and metadata processing. Updated related bytecode handling to use this new implementation.
KTIJ-34048 Add message collector support
KTIJ-34048 Add Kotlin compiler arguments processing
KTIJ-34048 Add tracker processing for Kotlin compiler runner in Bazel
Enhanced the KotlinCompilerRunner to process generated files and extract data such as inline constants, enum-when expressions, imports, and lookup usages. Introduced processing methods for these trackers and ensured proper initialization for robust build services.
KTIJ-34048 Implement Kotlin compiler pipeline for Bazel integration
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
extract bazel inc builder and dep graph into separate modules
jps-builders-6 moved
less dependencies on platform modules
rules_jvm: dummy BUILD.bazel for dependency-graph and jvm-inc-builder
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
jps-to-bazel: support shared modules in bazel generator
extract bazel inc builder and dep graph into separate modules
Merge remote-tracking branch 'origin/jeka/bazel-inc-builder' into jeka/bazel-inc-builder
Merge remote-tracking branch 'origin/jeka/bazel-inc-builder' into jeka/bazel-inc-builder
# Conflicts:
# .idea/modules.xml
# community/build/jvm-rules/jvm-inc-builder/BUILD.bazel
# community/build/jvm-rules/jvm-inc-builder/src/org/jetbrains/jps/bazel/impl/JavaCompilerRunner.java
# community/build/jvm-rules/jvm-inc-builder/src/org/jetbrains/jps/bazel/impl/ModulePathSplitter.java
# community/platform/build-scripts/bazel/src/org/jetbrains/intellij/build/bazel/BazelBuildFileGenerator.kt
Add patched Kotlin compiler for Bazel
KTIJ-34048 cleanups and refactorings, TODOs added
KTIJ-34048 Rename pipeline.kt to kotlinPipeline.kt for clarity
The file rename reflects its specific purpose related to Kotlin. This improves code readability and aligns with naming conventions.
KTIJ-34048 Add support for Kotlin compiler configuration updates
Introduce a configuration updater in BazelJvmCliPipeline to enable dynamic updates to the Kotlin compiler configuration. This includes a new pipeline phase, `BazelConfigurationUpdaterPipelinePhase`, ensuring configurations can be modified during the compilation process.
KTIJ-34048 Don't use GeneratedJvmClass because it depends on filesystem
Replaced GeneratedJvmClass with KotlinJvmGeneratedFile for .class outputs to improve handling and clarity. Introduced KotlinJvmGeneratedFile as a new class to encapsulate relevant logic, ensuring better separation of concerns and metadata processing. Updated related bytecode handling to use this new implementation.
KTIJ-34048 Add message collector support
KTIJ-34048 Add Kotlin compiler arguments processing
KTIJ-34048 Add tracker processing for Kotlin compiler runner in Bazel
Enhanced the KotlinCompilerRunner to process generated files and extract data such as inline constants, enum-when expressions, imports, and lookup usages. Introduced processing methods for these trackers and ensured proper initialization for robust build services.
KTIJ-34048 Implement Kotlin compiler pipeline for Bazel integration
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
extract bazel inc builder and dep graph into separate modules
jps-builders-6 moved
less dependencies on platform modules
rules_jvm: dummy BUILD.bazel for dependency-graph and jvm-inc-builder
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
jps-to-bazel: support shared modules in bazel generator
extract bazel inc builder and dep graph into separate modules
KTIJ-34048 cleanups and refactorings, TODOs added
KTIJ-34048 Rename pipeline.kt to kotlinPipeline.kt for clarity
The file rename reflects its specific purpose related to Kotlin. This improves code readability and aligns with naming conventions.
KTIJ-34048 Add support for Kotlin compiler configuration updates
Introduce a configuration updater in BazelJvmCliPipeline to enable dynamic updates to the Kotlin compiler configuration. This includes a new pipeline phase, `BazelConfigurationUpdaterPipelinePhase`, ensuring configurations can be modified during the compilation process.
KTIJ-34048 Don't use GeneratedJvmClass because it depends on filesystem
Replaced GeneratedJvmClass with KotlinJvmGeneratedFile for .class outputs to improve handling and clarity. Introduced KotlinJvmGeneratedFile as a new class to encapsulate relevant logic, ensuring better separation of concerns and metadata processing. Updated related bytecode handling to use this new implementation.
KTIJ-34048 Add message collector support
KTIJ-34048 Add Kotlin compiler arguments processing
KTIJ-34048 Add tracker processing for Kotlin compiler runner in Bazel
Enhanced the KotlinCompilerRunner to process generated files and extract data such as inline constants, enum-when expressions, imports, and lookup usages. Introduced processing methods for these trackers and ensured proper initialization for robust build services.
KTIJ-34048 Implement Kotlin compiler pipeline for Bazel integration
rules_jvm: dummy BUILD.bazel for dependency-graph and jvm-inc-builder
jps: name shared modules (between rules_jvm and monorepo) according to intellij convention
jps-to-bazel: support shared modules in bazel generator
extract bazel inc builder and dep graph into separate modules
Co-authored-by: Aleksei Cherepanov <aleksei.cherepanov@jetbrains.com>
Co-authored-by: Leonid Shalupov <leonid.shalupov@jetbrains.com>
Merge-request: IJ-MR-162577
Merged-by: Eugene Zhuravlev <eugene.zhuravlev@jetbrains.com>
GitOrigin-RevId: 758f1d24f368499a968a88d3004a2402d9a1f8ed
This way we don't need to specify them in the plugin layout manually. Also, we need to convert all modules in the Java plugin to content modules to get rid of an additional "Java Extension for Remote Client" plugin.
GitOrigin-RevId: 90956b93078784ffcea5f75038e86a4ae4846488
'client' directory is renamed to 'frontend-split' to be consistent with the actual naming schema. Consistent names are also needed to avoid changes in the layout when the JAR names for modules used by the split frontend process will be chosen automatically (IJPL-170362).
GitOrigin-RevId: 990d31cfae970579fa17119dd3869bb162b11923
