[
https://issues.apache.org/jira/browse/NETBEANS-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic updated NETBEANS-5610:
--------------------------------------
Attachment: gradleproject.log
> Gradle project loaded several times during project open
> -------------------------------------------------------
>
> Key: NETBEANS-5610
> URL: https://issues.apache.org/jira/browse/NETBEANS-5610
> Project: NetBeans
> Issue Type: Bug
> Components: lsp, projects - Gradle
> Reporter: Svatopluk Dedic
> Assignee: Svatopluk Dedic
> Priority: Major
> Labels: performance, race-condition
> Attachments: gradleproject.log
>
>
> 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]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
