You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Third party (external) artifacts can be brought in with systems such as [`rules_jvm_external`](https://github.com/bazelbuild/rules_jvm_external) or [`bazel_maven_repository`](https://github.com/square/bazel_maven_repository) or [`bazel-deps`](https://github.com/johnynek/bazel-deps), but make sure the version you use doesn't naively use `java_import`, as this will cause bazel to make an interface-only (`ijar`), or ABI jar, and the native `ijar` tool does not know about kotlin metadata with respect to inlined functions, and will remove method bodies inappropriately. Recent versions of `rules_jvm_external` and `bazel_maven_repository` are known to work with Kotlin.
149
149
150
-
# Development Setup Guide
151
-
As of 1.5.0, to use the rules directly from the rules_kotlin workspace (i.e. not the release artifact)
152
-
require the use of `release_archive` repository. This repository will build and configure the current
153
-
workspace to use `rules_kotlin` in the same manner as the released binary artifact.
150
+
## Development Setup
154
151
155
-
In the project's `WORKSPACE`, change the setup:
152
+
For local development of rules_kotlin:
156
153
157
-
```python
154
+
#### With Bzlmod
158
155
159
-
# Use local check-out of repo rules (or a commit-archive from github via http_archive or git_repository)
0 commit comments