You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Laszlo Kishalmi (Jira)" <ji...@apache.org> on 2020/12/09 16:12:00 UTC

[jira] [Commented] (NETBEANS-5130) Bigger projects during scanning present IDE error in notifications and present fake errors

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

Laszlo Kishalmi commented on NETBEANS-5130:
-------------------------------------------

Can I have more information. Like ide logs on NPE. It might happen that the IDE got an NPE during parsing and that cause this issue. You may try it with or without nb-javac.

> Bigger projects during scanning present IDE error in notifications and present fake errors
> ------------------------------------------------------------------------------------------
>
>                 Key: NETBEANS-5130
>                 URL: https://issues.apache.org/jira/browse/NETBEANS-5130
>             Project: NetBeans
>          Issue Type: Bug
>          Components: ide - UI, java - Editor, platform - Action Items, projects - Gradle
>    Affects Versions: 12.2
>         Environment: OpenJDK 11.0.2+
> Gradle 6.4.1, 6.7.1
>            Reporter: Netbeans User 2019
>            Assignee: Laszlo Kishalmi
>            Priority: Critical
>              Labels: gradle, performance
>
> Window > IDE Tools > Notifications
> Priority / Message               / Date Created   / Category
> Zz       / unexpected Exception  / 1 minutes ago  / Error
> After click on link for reporting of issue and click to be shown details
> so there is only text: java.lang.NullPointerException 
> Additionally it is seen that "Background scanning of projects..." takes really enormous amount of time on project with hundred of classes that ends with such fake errors and notification above.
> Some classes reports fake errors that it is not possible to fix by any of these ways:
> - close project and open
> - reload project
> - clean and build
> - scan for external changes
> - modification of file
> - creation new file in same folder and remove
> - removal of Apache Netbeans cache (under option --cachedir)
> - removal of caches/6.4.1 under gradle home
> So only way what helps:
> Opening step by step each such classes where such methods are implemented or to theirs return types of methods and so on and renaming such targeted classes that seems lead to an invocation of "Background scanning of projects..." on source file that leads to disappear such fake errors. Take to consideration also that some classes seems as they do not exist even in dialog for Type (CTRL+T).
> So I guess that it should be revised a "Background scanning of projects...".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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