[
https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662775#comment-16662775
]
Christian Lenz commented on NETBEANS-168:
-----------------------------------------
I come up with this problem again. I attached my messages.log. What I did:
- Clean NetBeans 10.0 VC1
- Open Project/Module Maven Projects (Incubator-netbeans/java/maven)
- Appeared the first time, I opened the project
- Appears again, after restarting NetBeans
> 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
> Attachments: messages.log
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
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
