[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink

["Christian Lenz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265833#comment-16265833 ] 

Christian Lenz commented on NETBEANS-168:
-----------------------------------------

I set it to critical, because it is an essential feature in NetBeans which blocks ofter other tasks and you can do anything while it is running. I don't mean, it will block the whole IDE but it will block the other tasks, they are running.

> 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)