0.1.3
New Features
- File paths reported for output are now relative to the compile working directory (if possible).
Change Log
commit eb51fa3
Author: Gunnar Wagenknecht gwagenknecht@salesforce.com
Date: Mon May 15 20:22:46 2023 +0200
Work around JDT absolute path issue. (#14)
This is a simple attempt to make paths in the output of the JDT compiler
relative again. Somehow they end up becoming absolute, which breaks IDEs
decided to rely on compiler output parsing for error reporting.
https://github.com/eclipse-jdt/eclipse.jdt.core/discussions/1061
WORKSPACE setup
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
name = "bazel_jdt_java_toolchain",
urls = [
"https://github.com/salesforce/bazel-jdt-java-toolchain/releases/download/0.1.3/rules_jdt-0.1.3.tar.gz",
],
sha256 = "b170a84a7b213b7a9975cdcda9391612a8642a3695727c8e0f66752aa77eae2e",
)
load("@bazel_jdt_java_toolchain//jdt:repositories.bzl", "rules_jdt_dependencies", "rules_jdt_toolchains")
rules_jdt_dependencies()
rules_jdt_toolchains()
Using the rules
See the source.