Initializing plugin in a mid-sized monorepo takes hours #129
Description
We have a monorepo with a couple of hundred subcomponents (as determined by find . -name BUILD.bazel in the monorepo root). Opening a subpath of that monorepo and initializing the plugin has been running for hours and I have no idea how long it's going to take until it completes.
A few steps I've noticed took a lot of time:
- Provisioning
.eclipseprojects for each java component Computing Bazel project classpathsfor a bunch of stuff; unclear to me what the scope of each of those is, because sometimes it seems like it's doing it for an entire package, and other times for just a single file.
At the step I'm currently at, every so often (a few times per minute?) the Java Build Status view outputs something like {hash} {repo-name}> bazel query //{path-to/subcomponent}:all [Done].
Is it expected that this extension doesn't work well with monorepos? Is it expected that it should take this long? (I thought monorepos was why you used Bazel, so that would surprise me...) How much of this work will be cached, and how much will have to happen every time I open a component in this monorepo? Will it matter if I've opened that exact component before or not?