You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Gili (JIRA)" <ji...@apache.org> on 2018/01/03 04:06:00 UTC
[jira] [Comment Edited] (NETBEANS-168) Background scanning process
needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309122#comment-16309122 ]
Gili edited comment on NETBEANS-168 at 1/3/18 4:05 AM:
-------------------------------------------------------
Assuming the cache could be updated transactionally, couldn't Netbeans use the previous cache snapshot until the new one is committed?
Or are you saying that for new projects (where there is no previous cache state) this is as good as a blocking process? If you're saying the latter then I don't think we can do better. Intellij behaves the same way. At the very least the user is free to open other projects, close existing ones, browse files, while the process completes.
was (Author: cowwoc):
Assuming the cache could be updated transactionally, couldn't Netbeans use the previous cache snapshot until the new one is committed?
> Background scanning process needs a rethink
> -------------------------------------------
>
> Key: NETBEANS-168
> URL: https://issues.apache.org/jira/browse/NETBEANS-168
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance, java - Platform, platform - Execution
> Affects Versions: 8.2, Next
> Environment: NetBeans 8.2, Windows 10 x64
> Reporter: Christian Lenz
> Priority: Critical
>
> Often, while cloning, switching branch, merging, opening etc. etc. NetBeans starts Background scanning for changes, but it is not real background, because everything what you want to do then, like changing the branch, commit, push, pull, open project, delete or whatever, is blocking by this task and you can't cancel it, because it is essential.
> Either we need to rethink about this process like to make everything or most of the stuff doing things in parallel or the task should really be cancelable. It is a pain in the ass for big projects when they start to scan for changes.
> It is a real world case because you acan see it when you work on NetBeans modules.
> Cheers
> Chris
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists