NetBeans background scanning projects takes too long

后端 未结 15 1373
-上瘾入骨i
-上瘾入骨i 2021-02-05 03:29

NetBeans background scanning projects takes too long. Every time when I open netbeans it scanning for ages. I used NetBeans 7.2 and it works perfecly. Now I formatted pc and rei

相关标签:
15条回答
  • 2021-02-05 03:34

    Having the same issue with 8.0.2 when a project has JS resources I tracked it down in my case to a problem with the javascript2 editor module which has been updated over the original version shipping with netbeans 8.0.2.

    I simply solved it by removing the updated module.

    On Linux:

    rm ~/.netbeans/8.0.2/modules/org-netbeans-modules-javascript2-editor.jar
    

    However, after letting the netbeans updater download the module a second time, the problem didn't appear again.

    In Netbeans 8.1, the location of this file is at: ide/modules/org-netbeans-modules-javascript2-editor.jar.

    0 讨论(0)
  • 2021-02-05 03:34

    I actually made a bug report for this issue. It was fixed and pushed to the update channels yesterday. So for anyone still having this specific bug, let Netbeans check for updates. :)

    Bugfix: https://netbeans.org/bugzilla/show_bug.cgi?id=250985

    0 讨论(0)
  • 2021-02-05 03:37

    It should be called foreground scanning of projects. Closing the program and restarting solves it for me sometimes.

    0 讨论(0)
  • 2021-02-05 03:39

    After latest update of Netbean 8.0.2 I have the same problem that scaning process did not stop and go forever with CPU usage on 25%.

    When I replace javascrip editor files in C:\Program Files\NetBeans 8.0.2\ide\modules on Windows 7 with old one then scaning project process start work again. You can take those file from this repo.

    0 讨论(0)
  • 2021-02-05 03:40

    Try the following :
    1) Go to Window-->Files. This opens the Files Tab.
    2) In the Files Tab for each opened project open the nbproject folder and inside it open the project.properties file.
    3) Now in this file below the property "excludes" there are file references listed for all your referred Libraries (JARs)
    4) There might be some repeated file references with paths that may be old or on someone else's machine(if you are working in a group and transferred projects from someone's machine)
    5) Delete those old path references.
    Example -
    excludes=
    file.reference.xyz.jar=../not/correct/path.jar //delete this line
    file.reference.xyz.jar-1=../correct/path.jar //remove -1
    ....
    includes=**

    6)Also locate the property "javac.classpath" and delete the unnecessary classpath entries corresponding to the deleted references as described above.
    Example -
    javac.classpath=\
    ${file.reference.xyz.jar}:\ //keep this line
    ${file.reference.xyz.jar-1}:\ //delete this line
    ....
    javac.compilerargs=

    7) So now the file reference mentioned in the file reference section and the javac.classpath property is same and points to a valid Library (JAR) address on your machine or network.
    Example -
    excludes=
    file.reference.xyz.jar=../correct/path.jar //the correct reference & path
    ....
    includes=**
    ....
    javac.classpath=\
    ${file.reference.xyz.jar}:\ //the correct classpath entry for reference
    ....
    javac.compilerargs=
    ....

    The reason the above procedure worked (in my case) is because it prevents Netbeans from scanning unnecessary Library paths that may not be present on your machine/network.

    0 讨论(0)
  • This problem is related to one of the project opened in your IDE. As I had been facing the same issue but, after spending two hours on that issue I finally fixed that. Close project one by one or check and close the project where background processing is taking time. After closing the project delete the .nbproject folder and re-import the same project into your IDE.

    0 讨论(0)
提交回复
热议问题