Bloop will compile multiple times the same bridge concurrently about bloop HOT 5 CLOSED

I'm removing that from the 0.1 milestone. #49 added a lock JVM-wide lock, we can wait a bit longer before getting a system-wide lock.

from bloop.

Do we care about this happening in different instances of bloop or within one instance of bloop? A simpler solution could be obtained by just focusing on the latter rather than the former.

from bloop.

In essence, what we want to do here is to have all bloop instances coordinate to compile and reuse the compiler bridge if it's missing. I think this is a great good first issue where we could get help from contributors 😄.

from bloop.

This is not a major issue for now -- just a nice to have. Removing from the milestone and leaving it for the future. Remember that this will most likely never happen because users are strongly recommended to only have one bloop server running.

from bloop.

I'm removing this from the issue tracker. This is not an issue we'll devote time to fix soon, and it's very difficult that will bite someone in the future.

from bloop.