rules_kotlin icon indicating copy to clipboard operation
rules_kotlin copied to clipboard

Bazel rules for Kotlin

Results 243 rules_kotlin issues
Sort by recently updated
recently updated
newest added

Hey there! # Summary I'm having issues getting a `java_plugin` run in the compile_phase of a mixed-mode `kt_jvm_library` on the Java sources. The only examples I can see are java...

This is a second attempt at getting a less intrusive version of KSP working with rules_kotlin based on some feedback in the previous PR. This approach relies on a kt_compiler_plugin...

Related to breaking Bazel change https://github.com/bazelbuild/continuous-integration/issues/1404 Likely because of this repository's dependency on an old version of rules_nodejs Example failure: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2590#0182aecd-b22e-4451-9ec9-4acabee5f50b

component: jvm
P0

The current coverage instrumentation does not allow configurations for exclusions as compared to `Maven` or `Gradle` where we could declare an exclusion configuration to exclude classes via patterns/globs ([example](https://www.baeldung.com/jacoco-report-exclude)). Looking...

type: enhancement
note: help wanted
component: jvm

In some ksp usage scenarios, you need to pass in apoption. But now rules does not implement this function. I tried to implement it with a options params. https://github.com/bazelbuild/rules_kotlin/pull/1103 Here's...

# Problem Kotlin jdeps do not collect many direct and indirect dependencies that are required for compilation. These missing jdep found dependencies were discovered as Airbnb tests a "jdeps compile-time...

Supporting the optional user.bazelrc file for machine specific options that we don't want checked into the rules.

## Issue Summary Outputs for `.jdeps` files from `kt_jvm_library` targets include the absolute path to `kotlin-stdlib.jar`. This means that cache entries which include these outputs are not shared with other...

type: bug
component: jvm

Moving the assertions over so that we are comparing the exact expected jdeps to the actual jdeps. This avoids us making changes that accidentally leak types between the different dependency...