[jira] [Created] (NETBEANS-5906) Navigator for Gradle Tasks broken

2021-08-09 Thread michael anderl (Jira)
michael anderl created NETBEANS-5906:


 Summary: Navigator for Gradle Tasks broken
 Key: NETBEANS-5906
 URL: https://issues.apache.org/jira/browse/NETBEANS-5906
 Project: NetBeans
  Issue Type: Bug
Affects Versions: Next, 12.5
 Environment: win10amd64

adoptjdk16.0.22+7

gradle 7.1.1
Reporter: michael anderl
 Fix For: 12.4


Click in Navigator to run a gradle task wont do anything.

In master and 12.5-beta1 this is broken. Nothing happens in the output 
window.

Works with the same settings in 12.4.

Clean, Build, Run from the icons do fine.

 

 



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

-
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

2019-02-25 Thread michael anderl (JIRA)


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

michael anderl commented on NETBEANS-168:
-

All I wrote was with the new new Gradle support, but i think it hat problems 
with my old .gradle and .nb-gradle files.

 

> 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, 9.0, 10.0
> Environment: NetBeans 8.2, Windows 10 x64
>Reporter: Christian Lenz
>Priority: Blocker
>  Labels: ca_survey, pull-request-available
> Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 
> vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z
>
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> Often, while cloning, switching branch, merging, opening etc. etc. NetBeans 
> starts Background scanning for changes, but it is not real background, 
> because everything what you want to do then, like changing the branch, 
> commit, push, pull, open project, delete or whatever, is blocking by this 
> task and you can't cancel it, because it is essential.
> Either we need to rethink about this process like to make everything or most 
> of the stuff doing things in parallel or the task should really be 
> cancelable. It is a pain in the ass for big projects when they start to scan 
> for changes. 
> It is a real world case because you acan see it when you work on NetBeans 
> modules.
> Cheers
> Chris



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



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

2019-02-25 Thread michael anderl (JIRA)


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

michael anderl commented on NETBEANS-168:
-

 

After removing the .gradle and .nb-gradle files from my gradle project and 
killing all the java processes (I think left over from gradle) after a restart 
the problem is gone.

I used the old gradle Module on the project. Now with NB-master with gradle I 
dont need it any more.

I try to reproduce it with the old .gradle .nb-gradle files.

 

 

> 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, 9.0, 10.0
> Environment: NetBeans 8.2, Windows 10 x64
>Reporter: Christian Lenz
>Priority: Blocker
>  Labels: ca_survey, pull-request-available
> Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 
> vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z
>
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> Often, while cloning, switching branch, merging, opening etc. etc. NetBeans 
> starts Background scanning for changes, but it is not real background, 
> because everything what you want to do then, like changing the branch, 
> commit, push, pull, open project, delete or whatever, is blocking by this 
> task and you can't cancel it, because it is essential.
> Either we need to rethink about this process like to make everything or most 
> of the stuff doing things in parallel or the task should really be 
> cancelable. It is a pain in the ass for big projects when they start to scan 
> for changes. 
> It is a real world case because you acan see it when you work on NetBeans 
> modules.
> Cheers
> Chris



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



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

2019-02-22 Thread michael anderl (JIRA)


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

michael anderl commented on NETBEANS-168:
-

do you want the dump with some special combination?

nb 11-vc01 or master or nb10

build with sun corretto 

run with openjdk 12-33 or 11?

 

> 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, 9.0, 10.0
> Environment: NetBeans 8.2, Windows 10 x64
>Reporter: Christian Lenz
>Priority: Blocker
>  Labels: ca_survey, pull-request-available
> Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 
> vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z
>
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> Often, while cloning, switching branch, merging, opening etc. etc. NetBeans 
> starts Background scanning for changes, but it is not real background, 
> because everything what you want to do then, like changing the branch, 
> commit, push, pull, open project, delete or whatever, is blocking by this 
> task and you can't cancel it, because it is essential.
> Either we need to rethink about this process like to make everything or most 
> of the stuff doing things in parallel or the task should really be 
> cancelable. It is a pain in the ass for big projects when they start to scan 
> for changes. 
> It is a real world case because you acan see it when you work on NetBeans 
> modules.
> Cheers
> Chris



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



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

2019-02-22 Thread michael anderl (JIRA)


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

michael anderl commented on NETBEANS-168:
-

Same here:

fresh userdir and cachedir and a fresh installation of nb (git master) and 
nbjavac 1.51 afterwards

when i open a big gradle subproject with many java files (1778 java files in 21 
folders) the background scanning of projects goes fast to 99% and stops (ui 
starts to freeze)

after a while and freeze i get some outofmemoryerrors: java heap space

got to kill nb with the task manager

in userdir/var/log/heapdump.hprof is about 1,8gb big.

this happens every time i open the project

thx

mike

 

 
*Product Version:* Apache NetBeans IDE Dev (Build 20190221-fa6d3a548783)  --> ( 
compiled with amazon-corretto-8.202.08.2 and ANT 1.10.5 )
*Java:* 12; OpenJDK 64-Bit Server VM 12+33
*Runtime:* OpenJDK Runtime Environment 12+33
*System:* Windows 7 version 6.1 running on amd64; UTF-8; de_AT (nb)
*User directory:* D:\01NB\userdir12
*Cache directory:* D:\01NB\cachedir12

java.lang.OutOfMemoryError: Java heap space
 at java.base/java.util.Arrays.copyOf(Arrays.java:3746)
 at 
java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:172)
 at 
java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:775)
 at java.base/java.lang.StringBuilder.append(StringBuilder.java:248)
 at 
java.base/jdk.internal.reflect.MethodAccessorGenerator.generateName(MethodAccessorGenerator.java:756)
 at 
java.base/jdk.internal.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:286)
 at 
java.base/jdk.internal.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:112)
 at 
java.base/jdk.internal.reflect.ReflectionFactory.generateConstructor(ReflectionFactory.java:520)
 at 
java.base/jdk.internal.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:512)
 at 
java.base/java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1516)
 at java.base/java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:509)
 at java.base/java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:484)
 at 
java.base/java.security.AccessController.executePrivileged(AccessController.java:750)
 at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:310)
 at java.base/java.io.ObjectStreamClass.(ObjectStreamClass.java:484)
 at java.base/java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:381)
 at 
java.base/java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1135)
 at 
java.base/java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:349)
 at 
org.netbeans.modules.uihandler.AfterRestartExceptions.save(AfterRestartExceptions.java:129)
 at 
org.netbeans.modules.uihandler.AfterRestartExceptions.schedule(AfterRestartExceptions.java:92)
 at org.netbeans.modules.uihandler.UIHandler.publish(UIHandler.java:149)
 at java.logging/java.util.logging.Logger.log(Logger.java:979)
 at java.logging/java.util.logging.Logger.doLog(Logger.java:1006)
 at java.logging/java.util.logging.Logger.log(Logger.java:1117)
 at org.netbeans.core.NbLifecycleManager.exit(NbLifecycleManager.java:212)
 at org.netbeans.core.NbLifecycleManager.exit(NbLifecycleManager.java:115)
 at 
org.netbeans.core.windows.view.ui.MainWindow$9.windowClosing(MainWindow.java:529)
 at 
java.desktop/java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:357)
 at 
java.desktop/java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:357)
 at 
java.desktop/java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:357)
 at 
java.desktop/java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:357)
 at java.desktop/java.awt.Window.processWindowEvent(Window.java:2068)

> 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, 9.0, 10.0
> Environment: NetBeans 8.2, Windows 10 x64
>Reporter: Christian Lenz
>Priority: Blocker
>  Labels: ca_survey, pull-request-available
> Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 
> vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z
>
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> 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 thi

[jira] [Created] (NETBEANS-2129) New Gradle Java Application doesn't check if Application exists in Path

2019-02-17 Thread michael anderl (JIRA)
michael anderl created NETBEANS-2129:


 Summary: New Gradle Java Application doesn't check if Application 
exists in Path
 Key: NETBEANS-2129
 URL: https://issues.apache.org/jira/browse/NETBEANS-2129
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 11.0
Reporter: michael anderl


When I create a new gradle java application, NB doesn't check if there is an 
existing java gradle application in the project folder. Instead it just creates 
a new one inside the existing one.

No error message like in NB9 or before

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists