[
https://issues.apache.org/jira/browse/NETBEANS-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284694#comment-17284694
]
Svatopluk Dedic commented on NETBEANS-5318:
-------------------------------------------
According to quick investigation, there are multiple issues that sum up to the
observed behaviour. WIll try to confirm them with either unit test, or at least
diagnostic log message for [~lkishalmi] to review.
* It seems that when the {{GradleProjectProblemProvider.call}} is run, the
Gradle project is loaded ( {{GradleProjectCache.loadProject ), }}but the
visible project object still remains the same. But the ProbleProvider reports a
result, that allows the infrastructure to proceed further. It fires reload for
the project (will be done asynchronously)
* During *asynchronous* reload, the project *reloads again*, this time
updating the live reference.
* The "UI" for ProjectProblems gets the {{Result}} and since it is marked as
'resolved', it re-asks all providers for problems again. Since the asynchronous
reload did not take place yet, it will *again* get an unprimed project problem
* There seems to be a *race condition* between reload assigning new value to
the project variable, and the {{GradleProjectProblemProvider. }}During
debugging, the evaluation was done again and again on the same instance. Need
to confirm...
> Gradle priming build in VSCode is asking again and again.
> ---------------------------------------------------------
>
> Key: NETBEANS-5318
> URL: https://issues.apache.org/jira/browse/NETBEANS-5318
> Project: NetBeans
> Issue Type: Bug
> Components: vscode
> Affects Versions: 12.3
> Environment: Ubuntu 20.04, GraalVM 21.0 Jdk 8.
> Reporter: Martin Balin
> Assignee: Svatopluk Dedic
> Priority: Major
> Fix For: 12.3
>
>
> Running VSNetBeans 12.3.286 with GraalVM Micronaut ext. Create Gradle MN
> project.
> VSNB asks for Gradle priming build many times, message:
> "NetBeans is about to invoke a Gradle build process of the project: demog.
> Executing Gradle can be potentially un-safe as it allows arbitrary code
> execution."
> I always answered OK, but it was appearing again and again.
> After that i invoked "Java: Compile workspace" and it built and also problem
> with underlined "package...." statement went away, this is great.
> Should to be fixed for 12.3 final.
>
--
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
