[jira] [Commented] (NETBEANS-238) Invoking code-complete in Maven projects is extremely slow
[
https://issues.apache.org/jira/browse/NETBEANS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314544#comment-16314544
]
Jan Lahoda commented on NETBEANS-238:
-
[~cowwoc] I am not sure why there should be a difference - the Jenkins build is
doing "ant build" + some tests (IIRC "ant build" is "ant build-nozip"+building
the binary zip, and "ant" will do "ant build-nozip"). Are you running the build
on JDK 9? ("ant tryme" will normally run on JDK 8.)
> 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: NETBEANS-238-experiment.diff,
> 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] [Created] (NETBEANS-250) Code-complete corrupts pom.xml when updating dependency version
Gili created NETBEANS-250:
-
Summary: Code-complete corrupts pom.xml when updating dependency
version
Key: NETBEANS-250
URL: https://issues.apache.org/jira/browse/NETBEANS-250
Project: NetBeans
Issue Type: Bug
Components: editor - Completion & Templates
Environment: Product Version: Apache NetBeans IDE Dev (Build
incubator-netbeans-release-163-on-20180105)
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
1. Open a pom.xml in a Maven project
2. Position the caret inside {{}} of a dependency
3. Hit CTRL+SPACE to bring up code-complete
4. Select a different version number than what is currently set
5. If you were changing the version number from 1.6.0 to 1.6.1 then
code-complete will change the line from:
1.6.0
to:
1.6.10
Essentially, the portion of the version that needs to change gets left behind,
along with a trailing
Expected behavior: Line should read "1.6.1"
This is a regression relative to version 8.2
--
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
[
https://issues.apache.org/jira/browse/NETBEANS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314453#comment-16314453
]
Gili commented on NETBEANS-238:
---
[~jlahoda] I took your diff, built Netbeans locally, and sure enough the issue
was gone. But then, I rebuilt Netbeans a second time without your diff, and the
issue was *still* gone.
There seems to be something fundamentally different between the builds put out
by Jenkins and what "ant" builds locally. Aside from the above issue being
magically gone, I noticed that the loading splash screen is consistently
different for local builds.
1. What is the difference between local builds and what Jenkins puts out? Why
would this magically fix this issue?
2. Can you please guide me how to end up with builds identical to what Jenkins
puts out so I can test your diff more reliably?
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: NETBEANS-238-experiment.diff,
> 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
