Compiler bridge resolution blocks CLI

[tindzk]

After updating Bloop from v1.3.2 to v1.3.4, Seed's integration tests stopped working.

The two failed CI runs (1, 2) both block on the first bloop compile <module> command during the compiler bridge resolution:

[D] Read-only classes directory /tmp/seed3630563884690033698/meta-module/build/bloop/classes-empty-example-js
[D] New rw classes directory /tmp/seed3630563884690033698/meta-module/build/bloop/bloop-internal-classes/example-js-BgYTCnGgTUiUlzKIq0Qvcg==
[D] No previous setup found, invalidating everything.
[D] No previous setup found, invalidating everything.
[D] Full compilation, no sources in previous analysis.
[D] Full compilation, no sources in previous analysis.
[D] All sources are invalidated.
[D] Initial set of included nodes:
[D] All sources are invalidated.
[D] Initial set of included nodes:
[D] Recompiling all sources: number of invalidated sources > 50.0% of all sources
[D] Recompiling all sources: number of invalidated sources > 50.0% of all sources
[D] Resolving ch.epfl.scala:compiler-bridge_2.12:1.3.0-M4+26-045d2c8c 

In case it helps, here is the generated Bloop project from a local test suite run.

This issue might be related to: #799

[jvican]

Thanks for opening the ticket! This issue was fixed in v1.3.5 (which hasn't yet been officially released but which can be resolved from the CI) and it's also fixed in master. Next official release will advertise that we fixed this bug.

[tindzk]

Great to hear.

Where are the latest builds published? I have checked Bintray, but there have not been any artefacts since v1.3.3.

[jvican]

Stable releases go to https://search.maven.org/artifact/ch.epfl.scala/bloop-frontend_2.12/1.3.5/jar. Binary has been dormant since we've done some changes in our build, I plan to add on-merge releases back soon.