[jira] [Commented] (NETBEANS-242) NullPointerException at org.netbeans.modules.java.source.indexing.VanillaCompileWorker

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-242:


Definitely not. There's lots of reasons nb-javac was created:

https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac

And read the pros and cons of vanilla javac from jDK 9 here:

https://cwiki.apache.org/confluence/display/NETBEANS/Java+Editor+Using+JDK+javac

> NullPointerException at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker
> --
>
> Key: NETBEANS-242
> URL: https://issues.apache.org/jira/browse/NETBEANS-242
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-release-152-on-20171231)
> Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
> Runtime: Java(TM) SE Runtime Environment 9.0.1+11
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
> User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
>Reporter: Gili
> Attachments: Price.java
>
>
> I saved a Java file and got this exception:
> {code}
> java.lang.NullPointerException
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:492)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:420)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitClass(TreeScanner.java:187)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:436)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:808)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitCompilationUnit(TreeScanner.java:144)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:591)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.dropMethodsAndErrors(VanillaCompileWorker.java:522)
> [catch] at 
> 

[jira] [Commented] (NETBEANS-242) NullPointerException at org.netbeans.modules.java.source.indexing.VanillaCompileWorker

[Gili (JIRA)]

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

Gili commented on NETBEANS-242:
---

Okay, confirmed. This exception is only thrown with JDK9 javac. nb-javac works 
fine.

What is Apache Netbeans' policy on the Java compilers? Are both fully supported?

> NullPointerException at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker
> --
>
> Key: NETBEANS-242
> URL: https://issues.apache.org/jira/browse/NETBEANS-242
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-release-152-on-20171231)
> Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
> Runtime: Java(TM) SE Runtime Environment 9.0.1+11
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
> User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
>Reporter: Gili
> Attachments: Price.java
>
>
> I saved a Java file and got this exception:
> {code}
> java.lang.NullPointerException
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:492)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:420)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitClass(TreeScanner.java:187)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:436)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:808)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitCompilationUnit(TreeScanner.java:144)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:591)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.dropMethodsAndErrors(VanillaCompileWorker.java:522)
> [catch] at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.compile(VanillaCompileWorker.java:283)
>   at 
> 

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

[Gili (JIRA)]

[ 
https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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-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

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

[Gili (JIRA)]

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

Gili commented on NETBEANS-168:
---

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

[jira] [Created] (NETBEANS-244) nb-javac notification under JDK9 is very easy to overlook

[Gili (JIRA)]

Gili created NETBEANS-244:
-

 Summary: nb-javac notification under JDK9 is very easy to overlook
 Key: NETBEANS-244
 URL: https://issues.apache.org/jira/browse/NETBEANS-244
 Project: NetBeans
  Issue Type: Improvement
  Components: java - Compiler
 Environment: Product Version: Apache NetBeans IDE Dev (Build 
incubator-netbeans-release-159-on-20180102)
Updates: Updates available
Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
Runtime: Java(TM) SE Runtime Environment 9.0.1+11
System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
Reporter: Gili


When running Apache Netbeans for the first time under JDK9, users are presented 
with a tiny notification in the bottom right corner prompting them to install 
nb-javac. The notification disappears after 3 seconds.

It took me days to notice this notification, and then only after being told to 
look for it.

I suggest changing the UI so the user has to make an explicit decision to 
install nb-javac or not. A modal dialog comes to mind. Baring that, please make 
the notification display more prominently, and stay open much longer.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Updated] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Gili (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NETBEANS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gili updated NETBEANS-238:
--
Attachment: code-complete-profiler.npss

[~GeertjanWielenga] I was going to say that I remember seeing this problem on 
8.2 final but then I ran across 
https://netbeans.org/bugzilla/show_bug.cgi?id=270632

Sure enough (I just checked) the problem does *not* occur in 8.2 final but did 
occur as far back as dev build 201705080001 (7 months after 8.2 was released). 
Notice that this bug report contains a profiler snapshot. It's not clear 
whether any committer ended up looking at it.

So good news: this is a regression so it should be fixable. I also don't 
believe the problem is in Maven's end (because it is a regression, and because 
of what I'm about to share below). It should be possible to undo the damage, 
once we figure out what changed.

I am attaching an updated IDE profiler dump for your review. This was collected 
using Apache Netbeans build 152. It shows that the Editor parser waits 7 
seconds to acquire a lock. The culprit seems to be a Thread called {{Inactive 
RequestProcessor thread \[Was:Flush UI 
Logs/org.netbeans.modules.uihandler.UIHandler$2WriteOut]}} that spends 5 
seconds invoking {{File.list()}} which invokes a Win32-specific implementation. 
It's not clear to me what files it is listing and whether this problem really 
is Win32-specific.

I'm going to need help from one of the committers to proceed further (either 
reproduce the problem on your end, under Windows, or give me ideas of what to 
try next).

Thank you.

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
> Attachments: SlowCodeCompleteAntAndMaven.zip, 
> code-complete-profiler.npss
>
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Commented] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-238:


Just to confirm something -- you're able to reproduce this in NetBeans IDE 8.2 
as well? I.e., the official NetBeans IDE 8.2 from 
https://netbeans.org/downloads?

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
> Attachments: SlowCodeCompleteAntAndMaven.zip
>
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Commented] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Gili (JIRA)]

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

Gili commented on NETBEANS-238:
---

[~GeertjanWielenga] In the above repro steps I have been using the version of 
Maven bundled with Netbeans (3.3.9) but I get the same problem with the latest 
version (3.5.2). Is there a way to leverage the "Profile the IDE" feature to 
figure out whether the problem lies on the IDE-end or Maven-end?

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
> Attachments: SlowCodeCompleteAntAndMaven.zip
>
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Commented] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-238:


Well, we could use NetBeans IDE 8.2 as well to reproduce this, since you're 
able to reproduce this there too. I think you have a generic problem with 
Maven, possibly. Which version of Maven are you using.

I'm on Mac, so not able to reproduce your environment 100%.

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
> Attachments: SlowCodeCompleteAntAndMaven.zip
>
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Commented] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Gili (JIRA)]

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

Gili commented on NETBEANS-238:
---

> FYI, for me the code completion in SlowCodecompleteMaven is instantaneous.

Interesting. I did my best to keep my test environment as vanilla as possible. 
My exact repro steps are as follows:

1. Delete or rename C:\Users\Gili\AppData\Roaming\NetBeans\dev
2. Delete or rename C:\Users\Gili\.m2
3. Launch Apache Netbeans build 152
4. Install nb-javac, restart IDE.
5. Agree to allowing anonymous usage data.
6. Open SlowCodeCompleteMaven. Open {{MyClass}}.
7. Wait for CPU usage to hit 0%.
8. Invoke code-complete.

Are you doing the same? Are you able to bring your environment as close as 
possible to mine (running under Windows, under the same JDK)?

My network connection is 25/10 Mbps and is idle at the moment of testing. 
Enabling the maven.search.remote plugin did not make a difference.

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
> Attachments: SlowCodeCompleteAntAndMaven.zip
>
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Commented] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-238:


FYI, for me the code completion in SlowCodecompleteMaven is instantaneous.

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
> Attachments: SlowCodeCompleteAntAndMaven.zip
>
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Commented] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-238:


So, this is specifically about Maven and NetBeans and is not related to 
nb-javac, javac or the version of NetBeans. Possibly connected to your network, 
etc, so, maybe this generic solution helps:

https://jaxenter.com/netbeans/keep-netbeans-nimble-with-maven-remote-search

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
> Attachments: SlowCodeCompleteAntAndMaven.zip
>
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Comment Edited] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Gili (JIRA)]

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

Gili edited comment on NETBEANS-238 at 1/2/18 7:34 PM:
---

Okay. Here is a concrete example with nb-javac enabled.

I created two projects. SlowCodeCompleteMaven, and SlowCodeCompleteAnt. They 
contain identical classes.

In SlowCodeCompleteMaven, I place the caret inside {{MyClass}} after 
{{firstMethod()}} and before the closing brace. I then hit CTRL+SPACE. The IDE 
takes 7 seconds to respond. I get identical timing with nb-javac disabled.
If I perform the same operation for an Ant project, the response is 
instantaneous.

I am attaching these projects to this issue. Please take a moment to confirm 
whether you can reproduce the problem on your end. Thank you.


was (Author: cowwoc):
Okay. Here is a concrete example with nb-javac enabled.

I created two projects. SlowCodeCompleteMaven, and SlowCodeCompleteAnt. They 
contain identical classes.

In SlowCodeCompleteMaven, I place the caret inside MyClass after 
`firstMethod()` and before the closing brace. I then hit CTRL+SPACE. The IDE 
takes 7 seconds to respond. I get identical timing with nb-javac disabled.
If I perform the same operation for an Ant project, the response is 
instantaneous.

I am attaching these projects to this issue. Please take a moment to confirm 
whether you can reproduce the problem on your end. Thank you.

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
> Attachments: SlowCodeCompleteAntAndMaven.zip
>
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Updated] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Gili (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NETBEANS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gili updated NETBEANS-238:
--
Attachment: SlowCodeCompleteAntAndMaven.zip

Okay. Here is a concrete example with nb-javac enabled.

I created two projects. SlowCodeCompleteMaven, and SlowCodeCompleteAnt. They 
contain identical classes.

In SlowCodeCompleteMaven, I place the caret inside MyClass after 
`firstMethod()` and before the closing brace. I then hit CTRL+SPACE. The IDE 
takes 7 seconds to respond. I get identical timing with nb-javac disabled.
If I perform the same operation for an Ant project, the response is 
instantaneous.

I am attaching these projects to this issue. Please take a moment to confirm 
whether you can reproduce the problem on your end. Thank you.

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
> Attachments: SlowCodeCompleteAntAndMaven.zip
>
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Commented] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-238:


Those are all the same, but built by different operating systems. Indeed, 
though the place to take the download from is 
https://builds.apache.org/job/incubator-netbeans-release.

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Commented] (NETBEANS-242) NullPointerException at org.netbeans.modules.java.source.indexing.VanillaCompileWorker

[Gili (JIRA)]

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

Gili commented on NETBEANS-242:
---

> When you start up Apache NetBeans, you get a notification inside NetBeans 
> about installing nb-javac.

Oh, I see it now. The notification gets dismissed 3 seconds later. I strongly 
suggest making this notice more prominent and longer-lasting (wait for the user 
to explicitly dismiss it one way or another). The dialog mentioned at 
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta 
for JDK8 looks much better than what I got under JDK9.

I'll give nb-javac a try now. Thank you.

> NullPointerException at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker
> --
>
> Key: NETBEANS-242
> URL: https://issues.apache.org/jira/browse/NETBEANS-242
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-release-152-on-20171231)
> Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
> Runtime: Java(TM) SE Runtime Environment 9.0.1+11
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
> User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
>Reporter: Gili
> Attachments: Price.java
>
>
> I saved a Java file and got this exception:
> {code}
> java.lang.NullPointerException
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:492)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:420)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitClass(TreeScanner.java:187)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:436)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:808)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitCompilationUnit(TreeScanner.java:144)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:591)
>   at 
> 

[jira] [Commented] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Gili (JIRA)]

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

Gili commented on NETBEANS-238:
---

[~GeertjanWielenga] I am running on Apache Netbeans (build 152 as mentioned in 
the Environment field). I downloaded the binary from 
https://builds.apache.org/job/incubator-netbeans-release/ ... Out of curiosity, 
what is the difference between this build and 
https://builds.apache.org/job/incubator-netbeans-windows/ (since I am running 
under Windows)?

I don't mind trying a different builds, with and without nb-javac, with and 
without Maven. I just want to understand the difference between the various 
builds to avoid any misunderstandings in future bug reports.

I thought that there was only one version number for Apache Netbeans builds and 
it came from https://builds.apache.org/job/incubator-netbeans-release/. Now 
that I see multiple build jobs and version numbers, what is the appropriate way 
to report version numbers when I report bugs? Thank you.

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Commented] (NETBEANS-242) NullPointerException at org.netbeans.modules.java.source.indexing.VanillaCompileWorker

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-242:


Details: 
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta

> NullPointerException at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker
> --
>
> Key: NETBEANS-242
> URL: https://issues.apache.org/jira/browse/NETBEANS-242
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-release-152-on-20171231)
> Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
> Runtime: Java(TM) SE Runtime Environment 9.0.1+11
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
> User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
>Reporter: Gili
> Attachments: Price.java
>
>
> I saved a Java file and got this exception:
> {code}
> java.lang.NullPointerException
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:492)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:420)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitClass(TreeScanner.java:187)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:436)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:808)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitCompilationUnit(TreeScanner.java:144)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:591)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.dropMethodsAndErrors(VanillaCompileWorker.java:522)
> [catch] at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.compile(VanillaCompileWorker.java:283)
>   at 
> 

[jira] [Commented] (NETBEANS-242) NullPointerException at org.netbeans.modules.java.source.indexing.VanillaCompileWorker

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-242:


When you start up Apache NetBeans, you get a notification inside NetBeans about 
installing nb-javac.

> NullPointerException at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker
> --
>
> Key: NETBEANS-242
> URL: https://issues.apache.org/jira/browse/NETBEANS-242
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-release-152-on-20171231)
> Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
> Runtime: Java(TM) SE Runtime Environment 9.0.1+11
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
> User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
>Reporter: Gili
> Attachments: Price.java
>
>
> I saved a Java file and got this exception:
> {code}
> java.lang.NullPointerException
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:492)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:420)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitClass(TreeScanner.java:187)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:436)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:808)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitCompilationUnit(TreeScanner.java:144)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:591)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.dropMethodsAndErrors(VanillaCompileWorker.java:522)
> [catch] at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.compile(VanillaCompileWorker.java:283)
>   at 
> 

[jira] [Commented] (NETBEANS-242) NullPointerException at org.netbeans.modules.java.source.indexing.VanillaCompileWorker

[Gili (JIRA)]

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

Gili commented on NETBEANS-242:
---

[~GeertjanWielenga] Yes, this is with Apache Netbeans (see the Environment 
field above for the specific build number).

This is with JDK9. I asked in another issue where to download nb-javac but I 
did not receive a reply. If you could kindly point me in the right direction 
I'll try reproducing with it as well. Thank you.

> NullPointerException at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker
> --
>
> Key: NETBEANS-242
> URL: https://issues.apache.org/jira/browse/NETBEANS-242
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-release-152-on-20171231)
> Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
> Runtime: Java(TM) SE Runtime Environment 9.0.1+11
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
> User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
>Reporter: Gili
> Attachments: Price.java
>
>
> I saved a Java file and got this exception:
> {code}
> java.lang.NullPointerException
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:492)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:420)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitClass(TreeScanner.java:187)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:436)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:808)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitCompilationUnit(TreeScanner.java:144)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:591)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.dropMethodsAndErrors(VanillaCompileWorker.java:522)
> [catch] 

[incubator-netbeans] 01/01: Merge pull request #352 from alexvsimon/integration_alexvsimon

[matthiasblaesing]

This is an automated email from the ASF dual-hosted git repository.

matthiasblaesing pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans.git

commit 98e6ccf2631156a2efd983a2d4278e908c64ba8e
Merge: 95a3a8c 9dddad1
Author: Matthias Bläsing 
AuthorDate: Tue Jan 2 19:51:16 2018 +0100

Merge pull request #352 from alexvsimon/integration_alexvsimon

Integrate CND team changes in platform

 java.api.common/manifest.mf   |  2 +-
 java.api.common/nbproject/project.xml |  1 +
 .../netbeans/modules/bugtracking/commons/UndoRedoSupport.java | 11 +++
 .../org/netbeans/modules/versioning/util/UndoRedoSupport.java | 11 +++
 4 files changed, 16 insertions(+), 9 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
"commits@netbeans.apache.org" .

-
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

[jira] [Created] (NETBEANS-243) Enhance the project node to show more/all of the files found in the root node of the app.

[Dawn Raison (JIRA)]

Dawn Raison created NETBEANS-243:


 Summary: Enhance the project node to show more/all of the files 
found in the root node of the app.
 Key: NETBEANS-243
 URL: https://issues.apache.org/jira/browse/NETBEANS-243
 Project: NetBeans
  Issue Type: Improvement
  Components: projects - Maven
Affects Versions: 8.2
Reporter: Dawn Raison


There are an increasing number of configuration files that need to be accessed 
when developed applications (especially prevalent with compiled TS/JS type 
applications) that cannot be accessed from the projects view.
It would be useful to allow these files to appear under the "project files" 
node of the project view, to avoid having to switch back and forth between the 
project view and files view.

There already exists a plugin that can do some of this: 
https://github.com/geertjanw/FullMavenProjectFilesNode - should this 
functionality become standard to the IDE?

Some example files are  tsconfig.json, package.json, gulpfile.js, 
webpack.config.js, .gitignore



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[incubator-netbeans] 01/01: Merge pull request #350 from jlahoda/NETBEANS-234

[geertjan]

This is an automated email from the ASF dual-hosted git repository.

geertjan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans.git

commit 95a3a8c96658e3885af44005eccda53be46ec40a
Merge: a5f9d8e 9170746
Author: Geertjan Wielenga 
AuthorDate: Tue Jan 2 14:45:30 2018 +0100

Merge pull request #350 from jlahoda/NETBEANS-234

[NETBEANS-234] Fixing handling of broken generics in fields.

 .../java/source/indexing/VanillaCompileWorker.java |  4 +---
 .../java/source/indexing/VanillaCompileWorkerTest.java | 18 ++
 2 files changed, 19 insertions(+), 3 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
"commits@netbeans.apache.org" .

-
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

[incubator-netbeans] branch master updated (a5f9d8e -> 95a3a8c)

[geertjan]

This is an automated email from the ASF dual-hosted git repository.

geertjan pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans.git.


from a5f9d8e  Merge pull request #351 from cowwoc/master
 add 9170746  [NETBEANS-234] Fixing handling of broken generics in fields.
 new 95a3a8c  Merge pull request #350 from jlahoda/NETBEANS-234

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../java/source/indexing/VanillaCompileWorker.java |  4 +---
 .../java/source/indexing/VanillaCompileWorkerTest.java | 18 ++
 2 files changed, 19 insertions(+), 3 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
['"commits@netbeans.apache.org" '].

-
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

[jira] [Commented] (NETBEANS-242) NullPointerException at org.netbeans.modules.java.source.indexing.VanillaCompileWorker

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-242:


Is this with Apache NetBeans from here: 
https://builds.apache.org/job/incubator-netbeans-release/

Is this with nb-javac or javac from JDK 9, i.e., are you running on Java 9 and 
therefore using javac from there or have you installed nb-javac? Does this also 
occur with nb-javac?

> NullPointerException at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker
> --
>
> Key: NETBEANS-242
> URL: https://issues.apache.org/jira/browse/NETBEANS-242
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-release-152-on-20171231)
> Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
> Runtime: Java(TM) SE Runtime Environment 9.0.1+11
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
> User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
>Reporter: Gili
> Attachments: Price.java
>
>
> I saved a Java file and got this exception:
> {code}
> java.lang.NullPointerException
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:492)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:420)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitClass(TreeScanner.java:187)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:436)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:808)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitCompilationUnit(TreeScanner.java:144)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:591)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.dropMethodsAndErrors(VanillaCompileWorker.java:522)
> [catch] at 
> 

[jira] [Updated] (NETBEANS-242) NullPointerException at org.netbeans.modules.java.source.indexing.VanillaCompileWorker

[Gili (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NETBEANS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gili updated NETBEANS-242:
--
Attachment: Price.java

The file triggering the exception. Occurs 100% of the time I try saving.

> NullPointerException at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker
> --
>
> Key: NETBEANS-242
> URL: https://issues.apache.org/jira/browse/NETBEANS-242
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-release-152-on-20171231)
> Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
> Runtime: Java(TM) SE Runtime Environment 9.0.1+11
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
> User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
>Reporter: Gili
> Attachments: Price.java
>
>
> I saved a Java file and got this exception:
> {code}
> java.lang.NullPointerException
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:492)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:420)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitClass(TreeScanner.java:187)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:436)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:808)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitCompilationUnit(TreeScanner.java:144)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:591)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.dropMethodsAndErrors(VanillaCompileWorker.java:522)
> [catch] at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.compile(VanillaCompileWorker.java:283)
>   at 
> org.netbeans.modules.java.source.indexing.JavaCustomIndexer.index(JavaCustomIndexer.java:273)
>   at 
> 

[jira] [Comment Edited] (NETBEANS-242) NullPointerException at org.netbeans.modules.java.source.indexing.VanillaCompileWorker

[Gili (JIRA)]

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

Gili edited comment on NETBEANS-242 at 1/2/18 12:11 PM:


Attached {{Price.java}}, the file triggering the exception. Occurs 100% of the 
time I try saving.


was (Author: cowwoc):
The file triggering the exception. Occurs 100% of the time I try saving.

> NullPointerException at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker
> --
>
> Key: NETBEANS-242
> URL: https://issues.apache.org/jira/browse/NETBEANS-242
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-release-152-on-20171231)
> Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
> Runtime: Java(TM) SE Runtime Environment 9.0.1+11
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
> User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
>Reporter: Gili
> Attachments: Price.java
>
>
> I saved a Java file and got this exception:
> {code}
> java.lang.NullPointerException
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:492)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:420)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitClass(TreeScanner.java:187)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:436)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:380)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:808)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
>   at 
> jdk.compiler/com.sun.source.util.TreeScanner.visitCompilationUnit(TreeScanner.java:144)
>   at 
> jdk.compiler/com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:591)
>   at 
> jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
>   at 
> org.netbeans.modules.java.source.indexing.VanillaCompileWorker.dropMethodsAndErrors(VanillaCompileWorker.java:522)
> [catch] at 
> 

[jira] [Created] (NETBEANS-242) NullPointerException at org.netbeans.modules.java.source.indexing.VanillaCompileWorker

[Gili (JIRA)]

Gili created NETBEANS-242:
-

 Summary: NullPointerException at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker
 Key: NETBEANS-242
 URL: https://issues.apache.org/jira/browse/NETBEANS-242
 Project: NetBeans
  Issue Type: Bug
  Components: java - Source
 Environment: Product Version: Apache NetBeans IDE Dev (Build 
incubator-netbeans-release-152-on-20171231)
Java: 9.0.1; Java HotSpot(TM) 64-Bit Server VM 9.0.1+11
Runtime: Java(TM) SE Runtime Environment 9.0.1+11
System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
Reporter: Gili


I saved a Java file and got this exception:

{code}
java.lang.NullPointerException
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:492)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:517)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.resolveErrors(VanillaCompileWorker.java:518)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:485)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.error2Object(VanillaCompileWorker.java:507)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:420)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitMethod(VanillaCompileWorker.java:380)
at 
jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:898)
at 
jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
at 
jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
at 
jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
at 
jdk.compiler/com.sun.source.util.TreeScanner.visitClass(TreeScanner.java:187)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:436)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$3.visitClass(VanillaCompileWorker.java:380)
at 
jdk.compiler/com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:808)
at 
jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
at 
jdk.compiler/com.sun.source.util.TreeScanner.scan(TreeScanner.java:105)
at 
jdk.compiler/com.sun.source.util.TreeScanner.scanAndReduce(TreeScanner.java:113)
at 
jdk.compiler/com.sun.source.util.TreeScanner.visitCompilationUnit(TreeScanner.java:144)
at 
jdk.compiler/com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:591)
at 
jdk.compiler/com.sun.source.util.TreePathScanner.scan(TreePathScanner.java:82)
at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker.dropMethodsAndErrors(VanillaCompileWorker.java:522)
[catch] at 
org.netbeans.modules.java.source.indexing.VanillaCompileWorker.compile(VanillaCompileWorker.java:283)
at 
org.netbeans.modules.java.source.indexing.JavaCustomIndexer.index(JavaCustomIndexer.java:273)
at 
org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor$2.run(Indexable.java:138)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runIndexer(RepositoryUpdater.java:275)
at 
org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor.index(Indexable.java:136)
at 
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doIndex(RepositoryUpdater.java:2750)
at 

[jira] [Commented] (NETBEANS-217) ClassCastException when editing Git commit message

[Antonio Vieiro (JIRA)]

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

Antonio Vieiro commented on NETBEANS-217:
-

@see https://github.com/apache/incubator-netbeans/pull/352

> ClassCastException when editing Git commit message
> --
>
> Key: NETBEANS-217
> URL: https://issues.apache.org/jira/browse/NETBEANS-217
> Project: NetBeans
>  Issue Type: Bug
>  Components: versioncontrol - Git
>Affects Versions: 9.0
> Environment: Windows 10
> Java 9
> Build: incubator-netbeans-linux-268-on-20171213
>Reporter: Thomas Kellerer
>  Labels: Java9-IDE
>
> When editing the commit message in a Git commit window, every keystroke 
> generates the following exception:
> {noformat}
> java.lang.ClassCastException: 
> java.desktop/javax.swing.text.AbstractDocument$DefaultDocumentEventUndoableWrapper
>  cannot be cast to 
> java.desktop/javax.swing.text.AbstractDocument$DefaultDocumentEvent
>   at 
> org.netbeans.modules.versioning.util.UndoRedoSupport$CompoundUndoManager.undoableEditHappened(UndoRedoSupport.java:111)
>   at 
> java.desktop/javax.swing.text.AbstractDocument.fireUndoableEditUpdate(AbstractDocument.java:293)
>   at 
> java.desktop/javax.swing.text.AbstractDocument.handleRemove(AbstractDocument.java:632)
>   at 
> java.desktop/javax.swing.text.AbstractDocument.remove(AbstractDocument.java:596)
>   at 
> java.desktop/javax.swing.text.DefaultEditorKit$DeletePrevCharAction.actionPerformed(DefaultEditorKit.java:1075)
>   at 
> java.desktop/javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1805)
>   at 
> java.desktop/javax.swing.JComponent.processKeyBinding(JComponent.java:2901)
>   at 
> java.desktop/javax.swing.JComponent.processKeyBindings(JComponent.java:2949)
>   at 
> java.desktop/javax.swing.JComponent.processKeyEvent(JComponent.java:2863)
>   at java.desktop/java.awt.Component.processEvent(Component.java:6355)
>   at java.desktop/java.awt.Container.processEvent(Container.java:2259)
>   at 
> java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4961)
>   at 
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2317)
>   at java.desktop/java.awt.Component.dispatchEvent(Component.java:4793)
>   at 
> java.desktop/java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1955)
>   at 
> java.desktop/java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:827)
>   at 
> java.desktop/java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:1096)
>   at 
> java.desktop/java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:966)
>   at 
> java.desktop/java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:792)
>   at 
> java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4842)
>   at 
> java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2317)
>   at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2758)
>   at java.desktop/java.awt.Component.dispatchEvent(Component.java:4793)
>   at 
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:766)
>   at java.desktop/java.awt.EventQueue.access$500(EventQueue.java:97)
>   at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:717)
>   at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:711)
>   at java.base/java.security.AccessController.doPrivileged(Native Method)
>   at 
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:89)
>   at 
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:99)
>   at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:739)
>   at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:737)
>   at java.base/java.security.AccessController.doPrivileged(Native Method)
>   at 
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:89)
>   at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:736)
>   at 
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> [catch] at 
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:199)
>   at 
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
>   at 
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:117)
>   at 
> java.desktop/java.awt.WaitDispatchSupport$2.run(WaitDispatchSupport.java:190)
>   at 
> 

[jira] [Comment Edited] (NETBEANS-241) Migrate Exception Reporter to Apache

[Gili (JIRA)]

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

Gili edited comment on NETBEANS-241 at 1/2/18 11:33 AM:


Issue collectors might work but I believe we're missing a middle piece (#2 
below). I'm aware of 3 pieces of the puzzle:

1. Analytics collection in the IDE.
2. Report tracker (as opposed to issue tracker which follows). Each report 
corresponds to a single occurrence of a bug in a user's IDE.
3. Issue tracker. Each issue corresponds to one or more reports in step 2.

The Reporter Tracker in step 2 consolidates related reports and does some 
intelligent things like:

1. Multiple reports with similar stack-traces get redirected to the same issue.
2. Only create a new issue once a bug has been reported multiple times, ideally 
by different users. Some reports are promoted into issues right away (e.g. 
NPEs) while others (IOExceptions) are not. I assume this is because some 
exceptions are more likely to be caused by user error than others (e.g. out of 
memory, out of diskspace, etc)
3. If a report corresponds to an issue that is marked as fixed, but the 
reporter is running a newer version of the IDE than the version the issue 
should be fixed in then the Exception Reporter automatically reopens the bug 
report with the relevant information.
4. If a report corresponds to an issue that is marked as fixed, but the 
reporter is running an older version of the IDE, the Exception Reporter points 
the user to the newer version so he can update.

So the question is: where does this piece sit? I don't believe JIRA has 
something to answer this question, though obviously nothing prevents us from 
wrapping this logic in a JIRA plugin. If we do so, other Apache (and 
non-Apache) projects stand to gain.


was (Author: cowwoc):
Issue collectors might work but I believe we're missing a middle piece (#2 
below). I'm aware of 3 pieces of the puzzle:

1. Analytics collection in the IDE.
2. Report tracker (as opposed to issue tracker which follows). Each report 
corresponds to a single occurrence of a bug in a user's IDE.
3. Issue tracker. Each issue corresponds to one or more reports in step 2.

The Reporter Tracker in step 2 consolidates related reports and does some 
intelligent things like:

1. Multiple reports with similar stack-traces get redirected to the same issue.
2. Only create a new issue once a bug has been reported multiple times, ideally 
by different users. Some reports are promoted into issues right away (e.g. 
NPEs) while others (IOExceptions) are not. I assume this is because some 
exceptions are more likely to be caused by user error than others (e.g. out of 
memory, out of diskspace, etc)
3. If a report corresponds to an issue that is marked as fixed, but the 
reporter is running a newer version of the IDE than the version the issue 
should be fixed in then the Exception Reporter automatically reopens the bug 
report with the relevant information.
4. If a report corresponds to an issue that is marked as fixed, but the 
reporter is running an older version of the IDE, the Exception Reporter points 
the user to the newer version so he can update.

> Migrate Exception Reporter to Apache
> 
>
> Key: NETBEANS-241
> URL: https://issues.apache.org/jira/browse/NETBEANS-241
> Project: NetBeans
>  Issue Type: Improvement
>  Components: ide - Logger
>Reporter: Gili
>
> Expected behavior: Exception Reporter should file bugs in the new Apache JIRA 
> issue tracker instead of the old Bugzilla system.
> It's not clear (to me at least) what metadata you need to store outside of 
> individual bug reports, so that needs to be fleshed out because Apache might 
> have provide the necessary infrastructure to host it.
> This issue is related to NETBEANS-164



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Commented] (NETBEANS-241) Migrate Exception Reporter to Apache

[Gili (JIRA)]

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

Gili commented on NETBEANS-241:
---

Issue collectors might work but I believe we're missing a middle piece (#2 
below). I'm aware of 3 pieces of the puzzle:

1. Analytics collection in the IDE.
2. Report tracker (as opposed to issue tracker which follows). Each report 
corresponds to a single occurrence of a bug in a user's IDE.
3. Issue tracker. Each issue corresponds to one or more reports in step 2.

The Reporter Tracker in step 2 consolidates related reports and does some 
intelligent things like:

1. Multiple reports with similar stack-traces get redirected to the same issue.
2. Only create a new issue once a bug has been reported multiple times, ideally 
by different users. Some reports are promoted into issues right away (e.g. 
NPEs) while others (IOExceptions) are not. I assume this is because some 
exceptions are more likely to be caused by user error than others (e.g. out of 
memory, out of diskspace, etc)
3. If a report corresponds to an issue that is marked as fixed, but the 
reporter is running a newer version of the IDE than the version the issue 
should be fixed in then the Exception Reporter automatically reopens the bug 
report with the relevant information.
4. If a report corresponds to an issue that is marked as fixed, but the 
reporter is running an older version of the IDE, the Exception Reporter points 
the user to the newer version so he can update.

> Migrate Exception Reporter to Apache
> 
>
> Key: NETBEANS-241
> URL: https://issues.apache.org/jira/browse/NETBEANS-241
> Project: NetBeans
>  Issue Type: Improvement
>  Components: ide - Logger
>Reporter: Gili
>
> Expected behavior: Exception Reporter should file bugs in the new Apache JIRA 
> issue tracker instead of the old Bugzilla system.
> It's not clear (to me at least) what metadata you need to store outside of 
> individual bug reports, so that needs to be fleshed out because Apache might 
> have provide the necessary infrastructure to host it.
> This issue is related to NETBEANS-164



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[incubator-netbeans] branch master updated (7cce405 -> a5f9d8e)

[geertjan]

This is an automated email from the ASF dual-hosted git repository.

geertjan pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans.git.


from 7cce405  When on Windows ignore file separator and case
 add 5f8cbe7  Added link to Jenkins builds
 add a3a13b3  Update in response to PR comments
 new a5f9d8e  Merge pull request #351 from cowwoc/master

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 README.md | 8 
 1 file changed, 8 insertions(+)

-- 
To stop receiving notification emails like this one, please contact
['"commits@netbeans.apache.org" '].

-
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

[incubator-netbeans] 01/01: Merge pull request #351 from cowwoc/master

[geertjan]

This is an automated email from the ASF dual-hosted git repository.

geertjan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans.git

commit a5f9d8e3719ee65bc876e5839f9f03512a803790
Merge: 7cce405 a3a13b3
Author: Geertjan Wielenga 
AuthorDate: Tue Jan 2 12:21:49 2018 +0100

Merge pull request #351 from cowwoc/master

Added link to Jenkins builds

 README.md | 8 
 1 file changed, 8 insertions(+)

-- 
To stop receiving notification emails like this one, please contact
"commits@netbeans.apache.org" .

-
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

[jira] [Commented] (NETBEANS-241) Migrate Exception Reporter to Apache

[Gili (JIRA)]

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

Gili commented on NETBEANS-241:
---

The value of the exception reporter is that it gathers and includes more 
contextual information alongside bug reports than users would normally include 
by themselves. This could be something as simple as the version build number 
but it also includes the exact sequence of steps that triggered the bug in the 
first place. Half the time I run across a bug I cannot recall the exact 
sequence of steps I invoked, but the exception reporter *does* and it includes 
this information on my behalf. It also automatically consolidates duplicate 
reports (based on stack-traces), saving committers' time. 

I can honestly say I wouldn't have filed 25% of the bug reports I have over the 
years if it wasn't for the exception reporter being around.

As for other Apache projects not having this mechanism: better to lift everyone 
up than to lower us down, don't you think? :)

> Migrate Exception Reporter to Apache
> 
>
> Key: NETBEANS-241
> URL: https://issues.apache.org/jira/browse/NETBEANS-241
> Project: NetBeans
>  Issue Type: Improvement
>  Components: ide - Logger
>Reporter: Gili
>
> Expected behavior: Exception Reporter should file bugs in the new Apache JIRA 
> issue tracker instead of the old Bugzilla system.
> It's not clear (to me at least) what metadata you need to store outside of 
> individual bug reports, so that needs to be fleshed out because Apache might 
> have provide the necessary infrastructure to host it.
> This issue is related to NETBEANS-164



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[jira] [Commented] (NETBEANS-241) Migrate Exception Reporter to Apache

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-241:


We need to ask Apache whether they can support this, i.e., I don't believe 
there are other Apache projects that have this behavior.

> Migrate Exception Reporter to Apache
> 
>
> Key: NETBEANS-241
> URL: https://issues.apache.org/jira/browse/NETBEANS-241
> Project: NetBeans
>  Issue Type: Improvement
>  Components: ide - Logger
>Reporter: Gili
>
> Expected behavior: Exception Reporter should file bugs in the new Apache JIRA 
> issue tracker instead of the old Bugzilla system.
> It's not clear (to me at least) what metadata you need to store outside of 
> individual bug reports, so that needs to be fleshed out because Apache might 
> have provide the necessary infrastructure to host it.
> This issue is related to NETBEANS-164



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[incubator-netbeans] 02/02: When on Windows ignore file separator and case

[jtulach]

This is an automated email from the ASF dual-hosted git repository.

jtulach pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans.git

commit 7cce405efc8ed171eff2f079e73f9f5607c05c59
Author: Jaroslav Tulach 
AuthorDate: Tue Jan 2 11:12:39 2018 +0100

When on Windows ignore file separator and case
---
 .../startup/layers/CountingSecurityManager.java| 48 +++---
 1 file changed, 33 insertions(+), 15 deletions(-)

diff --git 
a/core.startup/test/unit/src/org/netbeans/core/startup/layers/CountingSecurityManager.java
 
b/core.startup/test/unit/src/org/netbeans/core/startup/layers/CountingSecurityManager.java
index 0bc9c52..0e6bf79 100644
--- 
a/core.startup/test/unit/src/org/netbeans/core/startup/layers/CountingSecurityManager.java
+++ 
b/core.startup/test/unit/src/org/netbeans/core/startup/layers/CountingSecurityManager.java
@@ -29,6 +29,7 @@ import java.security.Permission;
 import java.util.Arrays;
 import java.util.Collections;
 import java.util.HashMap;
+import java.util.Locale;
 import java.util.Map;
 import java.util.Properties;
 import java.util.Set;
@@ -39,6 +40,8 @@ import java.util.logging.Logger;
 import junit.framework.Assert;
 import org.netbeans.core.startup.InstalledFileLocatorImpl;
 import org.openide.modules.Places;
+import org.openide.util.Exceptions;
+import org.openide.util.Utilities;
 
 /**
  *
@@ -61,6 +64,7 @@ final class CountingSecurityManager extends SecurityManager 
implements Callable<
 
 public static void initialize(String prefix, Mode mode, Set 
allowedFiles) {
 System.setProperty("counting.security.disabled", "true");
+inSubtree("", "");
 
 if (System.getSecurityManager() instanceof CountingSecurityManager) {
 // ok
@@ -161,7 +165,13 @@ final class CountingSecurityManager extends 
SecurityManager implements Callable<
 setCnt(getCnt() + 1);
 pw.println("checkRead: " + file);
 if (who.get(file) == null) {
-Exception now = new Exception("checkRead: " + file);
+File home = new File(System.getProperty("netbeans.home"));
+try {
+home = home.getCanonicalFile();
+} catch (IOException ex) {
+Exceptions.printStackTrace(ex);
+}
+Exception now = new Exception("canon: " + home + " home: " + 
System.getProperty("netbeans.home") + " dirs: " + dirs + " prefix: " + prefix + 
" checkRead: " + file);
 who.put(file, now);
 now.printStackTrace(pw);
 pw.flush();
@@ -172,7 +182,7 @@ final class CountingSecurityManager extends SecurityManager 
implements Callable<
 @Override
 public void checkRead(String file, Object context) {
 /*
-if (file.startsWith(prefix)) {
+if (inSubtree(file, prefix)) {
 cnt++;
 pw.println("checkRead2: " + file);
 }
@@ -385,7 +395,7 @@ final class CountingSecurityManager extends SecurityManager 
implements Callable<
 // still initializing
 return false;
 }
-if (!file.startsWith(ud)) {
+if (!inSubtree(file, ud)) {
 return false;
 }
 
@@ -408,7 +418,7 @@ final class CountingSecurityManager extends SecurityManager 
implements Callable<
 }
 }
 
-if (file.startsWith(ud)) {
+if (inSubtree(file, ud)) {
 if (f.startsWith("/")) {
 f = f.substring(1);
 }
@@ -417,11 +427,11 @@ final class CountingSecurityManager extends 
SecurityManager implements Callable<
 }
 }
 
-return prefix == null || file.startsWith(prefix);
+return prefix == null || inSubtree(file, prefix);
 }
 
 private boolean acceptFileRead(String file) {
-if (prefix != null && !file.startsWith(prefix)) {
+if (prefix != null && !inSubtree(file, prefix)) {
 return false;
 }
 if (acceptAll) {
@@ -433,7 +443,7 @@ final class CountingSecurityManager extends SecurityManager 
implements Callable<
 }
 for (Class c : this.getClassContext()) {
 if (c.getName().equals(InstalledFileLocatorImpl.class.getName())) {
-if (file.startsWith(Places.getCacheDirectory().getPath())) {
+if (inSubtree(file, Places.getCacheDirectory().getPath())) {
 return false;
 }
 if (file.equals(System.getProperty("netbeans.home"))) {
@@ -461,26 +471,26 @@ final class CountingSecurityManager extends 
SecurityManager implements Callable<
 if (file.endsWith("org-netbeans-modules-nbjunit.jar")) {
 return false;
 }
-if 
(file.startsWith(System.getProperty("java.home").replaceAll("[/][^/]*$",
 ""))) {
+if (inSubtree(file, 

[incubator-netbeans] branch master updated (301f641 -> 7cce405)

[jtulach]

This is an automated email from the ASF dual-hosted git repository.

jtulach pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans.git.


from 301f641  Randomly failed on Linux #296: 
https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-linux/296/
 new 431ce82  Removing the 8.3 test altogether
 new 7cce405  When on Windows ignore file separator and case

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../startup/layers/CountingSecurityManager.java| 48 +++---
 .../netbeans/modules/masterfs/URLMapperTest.java   | 25 ---
 2 files changed, 33 insertions(+), 40 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
['"commits@netbeans.apache.org" '].

-
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

[jira] [Commented] (NETBEANS-164) Remove gesture collector / error reporter / usage statistics from default build

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-164:


We need to ask Apache whether they can support these, i.e., I don't believe 
there are other Apache projects that have this behavior.

> Remove gesture collector / error reporter / usage statistics from default 
> build
> ---
>
> Key: NETBEANS-164
> URL: https://issues.apache.org/jira/browse/NETBEANS-164
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Logger
>Reporter: Emilian Bold
>  Labels: Java9-IDE
>
> It's unclear from a legal/infrastructure perspective how the existing UI 
> gesture collector / error reporter / usage statistics will work under Apache.
> So we should disable/remove it from the default IDE builds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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

[incubator-netbeans] 01/02: Removing the 8.3 test altogether

[jtulach]

This is an automated email from the ASF dual-hosted git repository.

jtulach pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans.git

commit 431ce82c09e793915df9c8b72143579a38a68c2d
Author: Jaroslav Tulach 
AuthorDate: Tue Jan 2 05:46:45 2018 +0100

Removing the 8.3 test altogether
---
 .../netbeans/modules/masterfs/URLMapperTest.java   | 25 --
 1 file changed, 25 deletions(-)

diff --git 
a/masterfs/test/unit/src/org/netbeans/modules/masterfs/URLMapperTest.java 
b/masterfs/test/unit/src/org/netbeans/modules/masterfs/URLMapperTest.java
index 462c5db..2e7f349 100644
--- a/masterfs/test/unit/src/org/netbeans/modules/masterfs/URLMapperTest.java
+++ b/masterfs/test/unit/src/org/netbeans/modules/masterfs/URLMapperTest.java
@@ -19,18 +19,12 @@
 
 package org.netbeans.modules.masterfs;
 
-import java.io.File;
-import java.net.URL;
-import org.junit.Assume;
-import static org.junit.Assume.assumeTrue;
 import org.netbeans.junit.NbTestCase;
 import org.netbeans.modules.masterfs.filebasedfs.FileBasedFileSystem;
 import org.openide.filesystems.FileObject;
 import org.openide.filesystems.FileSystem;
 import org.openide.filesystems.FileUtil;
-import org.openide.filesystems.URLMapper;
 import org.openide.util.Lookup;
-import org.openide.util.Utilities;
 import org.openide.util.lookup.Lookups;
 import org.openide.util.lookup.ServiceProvider;
 
@@ -51,25 +45,6 @@ public class URLMapperTest extends NbTestCase {
 assertEquals(MyInstance2.class, obj.getClass());
 }
 
-public void testNormalize8_3Names() throws Exception {
-if (!Utilities.isWindows()) {
-return;
-}
-
-clearWorkDir();
-File f = new File(getWorkDir(), "my new temp folder with long name");
-f.mkdirs();
-
-File shrtF = new File(getWorkDir(), "MYNEWT~1");
-assumeTrue("Short name exists", shrtF.isDirectory());
-
-final URL u = shrtF.toURI().toURL();
-final FileObject fo = URLMapper.findFileObject(u);
-File found = FileUtil.toFile(fo);
-
-assertEquals("The same file as original", f, found);
-}
-
 @ServiceProvider(service=Object.class)
 public static class MyInstance2 {
 public MyInstance2() {

-- 
To stop receiving notification emails like this one, please contact
"commits@netbeans.apache.org" .

-
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

[jira] [Commented] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow

[Geertjan Wielenga (JIRA)]

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

Geertjan Wielenga commented on NETBEANS-238:


Can you check to make sure that you're seeing this in Apache NetBeans, i.e., 
either after building the sources or after unzipping the daily build from here:

https://builds.apache.org/job/incubator-netbeans-linux

nb-jabvac is something you'll be asked to install at startup of Apache NetBeans 
(since it cannot be installed by default because it is not and will not be 
Apache licensed). First try without installing nb-javac, i.e., assuming you're 
on JDK 9 you'll then be using the vanilla javac from JDK 9. If you're able to 
reproduce the problem like that, install nb-javac as suggested by the IDE and 
try and reproduce there.

Is the problem specific to Maven in NetBeans or also to the standard Ant based 
projects? 

> Invoking code-complete in Maven projects is extremely slow
> --
>
> Key: NETBEANS-238
> URL: https://issues.apache.org/jira/browse/NETBEANS-238
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
> Environment: build 152
>Reporter: Gili
>Priority: Critical
>
> Say I'm in a class that has a field {{singletonScope}} where this class is 
> defined within the same Maven module.
> I type {{singletonScope.}} then wait for auto-complete to suggest possible 
> methods. Code-complete takes roughly 10 seconds to come back.
> This is reproducible 100% of the time.
> Expected behavior: Code-complete should complete within 300ms or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
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