To reproduce: get a LSP client, e.g. VSCode. get micronaut-test project, which is multi-project. In the LSP client, open a source from test-junit5.
I noticed that Gradle projects are loaded several times during LSP "project open" operation. The project first aims for FALLBACK and only then for FULL_ONLINE; maybe an issue with the 'priming' action.
But immediately after that the project again loads FALLBACK (from a RP, presumably a scheduled task from project open ?) and the again aiming FULL (from the projectOpened hook).
Finally the parent (root) project is opened - surprising at level FALLBACK - from WorkspaceServiceImpl.getTestRootURLs. Not sure if this quality level is sufficient for further operation: lkishalmi – what are the implications of getting the container project just to FALLBACK quality ?
// cc: dbalek