Gergely Fábián

How do I differentiate a V1 lock file from a V2 lock file?

I'm using a V2 lockfile I think, and I still can reproduce this issue. Just checked with building latest snapshot of zio, publishing it to local `.m2` and using at...

Now, this is strange. I have created a test right in rules_jvm_external. It works for: `ch.epfl.scala:compiler-interface:1.3.0-M4+47-d881fa2f` But it doesn't work for: `dev.zio:zio_2.12:2.1-RC1+39-8f391f96-SNAPSHOT` ``` "ch.epfl.scala:compiler-interface": { "shasums": { "jar": "d27afc405d935ba055d10f2c8aa2b884e5a090961bc9d1b0af596b3b547238e5" },...

I'll create a PR with a basic branch that adds tests for the compiler-interface, and then I can branch off from that to reproduce the error.

The basic case (that works) is reproduced in #1053.

Reproduction branch is here: https://github.com/gergelyfabian/rules_jvm_external/tree/tests_for_artifacts_with_plus_zio How to reproduce: ```shell git clone [email protected]:zio/zio.git cd zio sbt sbt:zio> ++2.12 sbt:zio> publishM2 git clone [email protected]:gergelyfabian/rules_jvm_external.git cd rules_jvm_external git checkout tests_for_artifacts_with_plus_zio tests/bazel_run_tests.sh ``` What...

> artifact.update({"url": "file://" + artifact["file"]}) Tried applying this fix, but it did not work. Works with the version from the PR #961.

Did you try playing with the --instrumentation_filter parameter?

Please check https://github.com/gergelyfabian/bazel-scala-example. I've updated it to use Bazel 5.3.2 and Java 17. On branch https://github.com/gergelyfabian/bazel-scala-example/tree/jacoco_coverage_fix_new I'm using a custom jacocorunner jar. Please try it by placing the custom built...

rules_scala is on version `73f5d1a7da081c9f5160b9ed7ac745388af28e23` in my example.