[jira] [Updated] (NETBEANS-3952) Netbeans 11.3 test windows takes null pointer exception when using gradle wrapper

2020-06-17 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi updated NETBEANS-3952:
---
   Attachment: errorTestWindow.txt
Affects Version/s: 12.0
  Description: 
java.lang.NullPointerException
 at 
org.netbeans.modules.gradle.test.GradleTestProgressListener.processTestOutput(GradleTestProgressListener.java:142)
 at 
org.netbeans.modules.gradle.test.GradleTestProgressListener.statusChanged(GradleTestProgressListener.java:80)
 at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
 at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
 at 
org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:42)
 at 
org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:231)
 at 
org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:150)
 at 
org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:141)
 at 
org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:37)
 at 
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
 at com.sun.proxy.$Proxy55.statusChanged(Unknown Source)
 at 
org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.broadcastTestOutputEvent(BuildProgressListenerAdapter.java:291)
 at 
org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.broadcastInternalProgressEvent(BuildProgressListenerAdapter.java:254)
 at 
org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.doBroadcast(BuildProgressListenerAdapter.java:213)
 at 
org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.onEvent(BuildProgressListenerAdapter.java:203)
 at 
org.gradle.tooling.internal.consumer.parameters.FailsafeBuildProgressListenerAdapter.onEvent(FailsafeBuildProgressListenerAdapter.java:39)
 at 
org.gradle.tooling.internal.consumer.parameters.FailsafeBuildProgressListenerAdapter.onEvent(FailsafeBuildProgressListenerAdapter.java:39)
 at 
org.gradle.tooling.internal.provider.ProviderConnection$BuildProgressListenerInvokingBuildEventConsumer.dispatch(ProviderConnection.java:313)
 at 
org.gradle.launcher.daemon.client.DaemonClient.monitorBuild(DaemonClient.java:222)
 at 
org.gradle.launcher.daemon.client.DaemonClient.executeBuild(DaemonClient.java:180)
 at 
org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:143)
 at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:94)
 at 
org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:51)
 at 
org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:35)
 at 
org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:60)
 at 
org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:38)
 at 
org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:193)
 at 
org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:136)
 at 
org.gradle.tooling.internal.provider.DefaultConnection.getModel(DefaultConnection.java:203)
 at 
org.gradle.tooling.internal.consumer.connection.CancellableModelBuilderBackedModelProducer.produceModel(CancellableModelBuilderBackedModelProducer.java:54)
 at 
org.gradle.tooling.internal.consumer.connection.PluginClasspathInjectionSupportedCheckModelProducer.produceModel(PluginClasspathInjectionSupportedCheckModelProducer.java:38)
 at 
org.gradle.tooling.internal.consumer.connection.AbstractConsumerConnection.run(AbstractConsumerConnection.java:62)
 at 
org.gradle.tooling.internal.consumer.connection.ParameterValidatingConsumerConnection.run(ParameterValidatingConsumerConnection.java:47)
 at 
org.gradle.tooling.internal.consumer.DefaultBuildLauncher$1.run(DefaultBuildLauncher.java:97)
 at 
org.gradle.tooling.internal.consumer.DefaultBuildLauncher$1.run(DefaultBuildLauncher.java:89)
 at 
org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:87)
 at 
org.gradle.tooling.internal.consumer.connection.CancellableConsumerActionExecutor.run(CancellableConsumerActionExecutor.java:45)
 at 
org.gradle.tooling.internal.consumer.connection.ProgressLoggingConsumerActionExecutor.run(ProgressLoggingConsumerActionExecutor.java:61)
 at 

[jira] [Updated] (NETBEANS-3952) Netbeans 11.3 test windows takes null pointer exception when using gradle wrapper

2020-05-11 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi updated NETBEANS-3952:
---
Summary: Netbeans 11.3 test windows takes null pointer exception when using 
gradle wrapper  (was: Netbeans 11.3 test windows take null pointer exception 
when using gradle wrapper)

> Netbeans 11.3 test windows takes null pointer exception when using gradle 
> wrapper
> -
>
> Key: NETBEANS-3952
> URL: https://issues.apache.org/jira/browse/NETBEANS-3952
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.3
> Environment: Linux interceptor 5.3.0-24-generic #26-Ubuntu SMP Thu 
> Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Andrea Paternesi
>Priority: Critical
>
> java.lang.NullPointerException
>  at 
> org.netbeans.modules.gradle.test.GradleTestProgressListener.processTestOutput(GradleTestProgressListener.java:142)
>  at 
> org.netbeans.modules.gradle.test.GradleTestProgressListener.statusChanged(GradleTestProgressListener.java:80)
>  at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:498)
>  at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
>  at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>  at 
> org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:42)
>  at 
> org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:231)
>  at 
> org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:150)
>  at 
> org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:141)
>  at 
> org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:37)
>  at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
>  at com.sun.proxy.$Proxy55.statusChanged(Unknown Source)
>  at 
> org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.broadcastTestOutputEvent(BuildProgressListenerAdapter.java:291)
>  at 
> org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.broadcastInternalProgressEvent(BuildProgressListenerAdapter.java:254)
>  at 
> org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.doBroadcast(BuildProgressListenerAdapter.java:213)
>  at 
> org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.onEvent(BuildProgressListenerAdapter.java:203)
>  at 
> org.gradle.tooling.internal.consumer.parameters.FailsafeBuildProgressListenerAdapter.onEvent(FailsafeBuildProgressListenerAdapter.java:39)
>  at 
> org.gradle.tooling.internal.consumer.parameters.FailsafeBuildProgressListenerAdapter.onEvent(FailsafeBuildProgressListenerAdapter.java:39)
>  at 
> org.gradle.tooling.internal.provider.ProviderConnection$BuildProgressListenerInvokingBuildEventConsumer.dispatch(ProviderConnection.java:313)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.monitorBuild(DaemonClient.java:222)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.executeBuild(DaemonClient.java:180)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:143)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:94)
>  at 
> org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:51)
>  at 
> org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:35)
>  at 
> org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:60)
>  at 
> org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:38)
>  at 
> org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:193)
>  at 
> org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:136)
>  at 
> org.gradle.tooling.internal.provider.DefaultConnection.getModel(DefaultConnection.java:203)
>  at 
> org.gradle.tooling.internal.consumer.connection.CancellableModelBuilderBackedModelProducer.produceModel(CancellableModelBuilderBackedModelProducer.java:54)
>  at 
> org.gradle.tooling.internal.consumer.connection.PluginClasspathInjectionSupportedCheckModelProducer.produceModel(PluginClasspathInjectionSupportedCheckModelProducer.java:38)
>  at 
> 

[jira] [Created] (NETBEANS-3952) Netbeans 11.3 test windows take null pointer exception when using gradle wrapper

2020-03-05 Thread Andrea Paternesi (Jira)
Andrea Paternesi created NETBEANS-3952:
--

 Summary: Netbeans 11.3 test windows take null pointer exception 
when using gradle wrapper
 Key: NETBEANS-3952
 URL: https://issues.apache.org/jira/browse/NETBEANS-3952
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 11.3
 Environment: Linux interceptor 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 
14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Reporter: Andrea Paternesi


java.lang.NullPointerException
 at 
org.netbeans.modules.gradle.test.GradleTestProgressListener.processTestOutput(GradleTestProgressListener.java:142)
 at 
org.netbeans.modules.gradle.test.GradleTestProgressListener.statusChanged(GradleTestProgressListener.java:80)
 at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
 at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
 at 
org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:42)
 at 
org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:231)
 at 
org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:150)
 at 
org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:141)
 at 
org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:37)
 at 
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
 at com.sun.proxy.$Proxy55.statusChanged(Unknown Source)
 at 
org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.broadcastTestOutputEvent(BuildProgressListenerAdapter.java:291)
 at 
org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.broadcastInternalProgressEvent(BuildProgressListenerAdapter.java:254)
 at 
org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.doBroadcast(BuildProgressListenerAdapter.java:213)
 at 
org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.onEvent(BuildProgressListenerAdapter.java:203)
 at 
org.gradle.tooling.internal.consumer.parameters.FailsafeBuildProgressListenerAdapter.onEvent(FailsafeBuildProgressListenerAdapter.java:39)
 at 
org.gradle.tooling.internal.consumer.parameters.FailsafeBuildProgressListenerAdapter.onEvent(FailsafeBuildProgressListenerAdapter.java:39)
 at 
org.gradle.tooling.internal.provider.ProviderConnection$BuildProgressListenerInvokingBuildEventConsumer.dispatch(ProviderConnection.java:313)
 at 
org.gradle.launcher.daemon.client.DaemonClient.monitorBuild(DaemonClient.java:222)
 at 
org.gradle.launcher.daemon.client.DaemonClient.executeBuild(DaemonClient.java:180)
 at 
org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:143)
 at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:94)
 at 
org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:51)
 at 
org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:35)
 at 
org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:60)
 at 
org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:38)
 at 
org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:193)
 at 
org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:136)
 at 
org.gradle.tooling.internal.provider.DefaultConnection.getModel(DefaultConnection.java:203)
 at 
org.gradle.tooling.internal.consumer.connection.CancellableModelBuilderBackedModelProducer.produceModel(CancellableModelBuilderBackedModelProducer.java:54)
 at 
org.gradle.tooling.internal.consumer.connection.PluginClasspathInjectionSupportedCheckModelProducer.produceModel(PluginClasspathInjectionSupportedCheckModelProducer.java:38)
 at 
org.gradle.tooling.internal.consumer.connection.AbstractConsumerConnection.run(AbstractConsumerConnection.java:62)
 at 
org.gradle.tooling.internal.consumer.connection.ParameterValidatingConsumerConnection.run(ParameterValidatingConsumerConnection.java:47)
 at 
org.gradle.tooling.internal.consumer.DefaultBuildLauncher$1.run(DefaultBuildLauncher.java:97)
 at 
org.gradle.tooling.internal.consumer.DefaultBuildLauncher$1.run(DefaultBuildLauncher.java:89)
 at 
org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:87)
 at 

[jira] [Commented] (NETBEANS-3720) Run focused test method and Debug focused test method disabled in certain circumstances

2020-01-21 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi commented on NETBEANS-3720:


Yes. The source folder is standard for gradle usage. So "src"  contains "main" 
and "test" directories. Each directory contains "java" and "resource" 
directories.

> Run focused test method and Debug focused test method disabled in certain 
> circumstances
> ---
>
> Key: NETBEANS-3720
> URL: https://issues.apache.org/jira/browse/NETBEANS-3720
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.2
> Environment: Kubuntu linux 19.10 64bit with java 8 64bit latest 
> version
>Reporter: Andrea Paternesi
>Priority: Major
>
> If you have a gradle project where the "main" source directory is not present 
> but there is only the "test" source directory then you cannot launch a test 
> using *Run focused test method* and *Debug focused test method* because 
> Netbeans simply disables them.
> If you create the "main/java"  directories with a simple readme file inside 
> then Netbeans enables again these two options.
> This is a bug to me. You can have a project with no main sources but test 
> sources.
> The example is to have a battery of end-to-end tests that simply calls rest 
> API.
> Can you please fix it?
> Thanks
>  



--
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] [Updated] (NETBEANS-3720) Run focused test method and Debug focused test method disabled in certain circumstances

2020-01-20 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi updated NETBEANS-3720:
---
Description: 
If you have a gradle project where the "main" source directory is not present 
but there is only the "test" source directory then you cannot launch a test 
using *Run focused test method* and *Debug focused test method* because 
Netbeans simply disables them.

If you create the "main/java"  directories with a simple readme file inside 
then Netbeans enables again these two options.

This is a bug to me. You can have a project with no main sources but test 
sources.

The example is to have a battery of end-to-end tests that simply calls rest API.

Can you please fix it?

Thanks

 

  was:
If you have a gradle project where the "main" source directory is not present 
but there is only the "test" source directory then you cannot launch a test 
using *Run focused test method* and *Debug focused test method* because 
Netbeans simply disables them.

If you create the "main"  directory with a simple readme file inside then 
Netbeans enables again these two options.

This is a bug to me. You can have a project with no main sources but test 
sources.

The example is to have a battery of end-to-end tests that simply calls rest API.

Can you please fix it?

Thanks

 


> Run focused test method and Debug focused test method disabled in certain 
> circumstances
> ---
>
> Key: NETBEANS-3720
> URL: https://issues.apache.org/jira/browse/NETBEANS-3720
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.2
> Environment: Kubuntu linux 19.10 64bit with java 8 64bit latest 
> version
>Reporter: Andrea Paternesi
>Priority: Major
>
> If you have a gradle project where the "main" source directory is not present 
> but there is only the "test" source directory then you cannot launch a test 
> using *Run focused test method* and *Debug focused test method* because 
> Netbeans simply disables them.
> If you create the "main/java"  directories with a simple readme file inside 
> then Netbeans enables again these two options.
> This is a bug to me. You can have a project with no main sources but test 
> sources.
> The example is to have a battery of end-to-end tests that simply calls rest 
> API.
> Can you please fix it?
> Thanks
>  



--
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] [Updated] (NETBEANS-3720) Run focused test method and Debug focused test method disabled in certain circumstances

2020-01-20 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi updated NETBEANS-3720:
---
Description: 
If you have a gradle project where the "main" source directory is not present 
but there is only the "test" source directory then you cannot launch a test 
using *Run focused test method* and *Debug focused test method* because 
Netbeans simply disables them.

If you create the "main"  directory with a simple readme file inside then 
Netbeans enables again these two options.

This is a bug to me. You can have a project with no main sources but test 
sources.

The example is to have a battery of end-to-end tests that simply calls rest API.

Can you please fix it?

Thanks

 

  was:
If you have a gradle project where the "main" source directory is not present 
but there is only the "test" source directory then you cannot launch a test 
using *Run focused test method* and *Debug focused test method because* 
Netbeans simply disables them.

If you create the "main"  directory with a simple readme file inside then 
Netbeans enables again these two options.

This is a bug to me. You can have a project with no main sources but test 
sources.

The example is to have a battery of end-to-end tests that simply calls rest API.

Can you please fix it?

Thanks

 


> Run focused test method and Debug focused test method disabled in certain 
> circumstances
> ---
>
> Key: NETBEANS-3720
> URL: https://issues.apache.org/jira/browse/NETBEANS-3720
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.2
> Environment: Kubuntu linux 19.10 64bit with java 8 64bit latest 
> version
>Reporter: Andrea Paternesi
>Priority: Major
>
> If you have a gradle project where the "main" source directory is not present 
> but there is only the "test" source directory then you cannot launch a test 
> using *Run focused test method* and *Debug focused test method* because 
> Netbeans simply disables them.
> If you create the "main"  directory with a simple readme file inside then 
> Netbeans enables again these two options.
> This is a bug to me. You can have a project with no main sources but test 
> sources.
> The example is to have a battery of end-to-end tests that simply calls rest 
> API.
> Can you please fix it?
> Thanks
>  



--
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] [Updated] (NETBEANS-3720) Run focused test method and Debug focused test method disabled in certain circumstances

2020-01-20 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi updated NETBEANS-3720:
---
Description: 
If you have a gradle project where the "main" source directory is not present 
but there is only the "test" source directory then you cannot launch a test 
using *Run focused test method* and *Debug focused test method because* 
Netbeans simply disables them.

If you create the "main"  directory with a simple readme file inside then 
Netbeans enables again these two options.

This is a bug to me. You can have a project with no main sources but test 
sources.

The example is to have a battery of end-to-end tests that simply calls rest API.

Can you please fix it?

Thanks

 

  was:
If you have a gradle project where the "main" source directory is not present 
but there is only the "test" source directory then you cannot launch test using 
*Run focused test method* and *Debug focused test method because* Netbeans 
simply disables them.

If you create the "main"  directory with a simple readme file inside then 
Netbeans enables again these two options.

This is a bug to me. You can have a project with no main sources but test 
sources.

The example is to have a battery of end-to-end tests that simply calls rest API.

Can you please fix it?

Thanks

 


> Run focused test method and Debug focused test method disabled in certain 
> circumstances
> ---
>
> Key: NETBEANS-3720
> URL: https://issues.apache.org/jira/browse/NETBEANS-3720
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.2
> Environment: Kubuntu linux 19.10 64bit with java 8 64bit latest 
> version
>Reporter: Andrea Paternesi
>Priority: Major
>
> If you have a gradle project where the "main" source directory is not present 
> but there is only the "test" source directory then you cannot launch a test 
> using *Run focused test method* and *Debug focused test method because* 
> Netbeans simply disables them.
> If you create the "main"  directory with a simple readme file inside then 
> Netbeans enables again these two options.
> This is a bug to me. You can have a project with no main sources but test 
> sources.
> The example is to have a battery of end-to-end tests that simply calls rest 
> API.
> Can you please fix it?
> Thanks
>  



--
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] [Created] (NETBEANS-3720) Run focused test method and Debug focused test method disabled in certain circumstances

2020-01-20 Thread Andrea Paternesi (Jira)
Andrea Paternesi created NETBEANS-3720:
--

 Summary: Run focused test method and Debug focused test method 
disabled in certain circumstances
 Key: NETBEANS-3720
 URL: https://issues.apache.org/jira/browse/NETBEANS-3720
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 11.2
 Environment: Kubuntu linux 19.10 64bit with java 8 64bit latest version
Reporter: Andrea Paternesi


If you have a gradle project where the "main" source directory is not present 
but there is only the "test" source directory then you cannot launch test using 
*Run focused test method* and *Debug focused test method because* Netbeans 
simply disables them.

If you create the "main"  directory with a simple readme file inside then 
Netbeans enables again these two options.

This is a bug to me. You can have a project with no main sources but test 
sources.

The example is to have a battery of end-to-end tests that simply calls rest API.

Can you please fix it?

Thanks

 



--
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-3385) Reload of dependencies in a gradle project always fails.

2019-11-23 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi commented on NETBEANS-3385:


Netbeans shows no errors in the log but the error comes out in the 
notification. I just attach the screenshot of the error below.

!NetbeansError.png!

> Reload of dependencies in a gradle project always fails.
> 
>
> Key: NETBEANS-3385
> URL: https://issues.apache.org/jira/browse/NETBEANS-3385
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: Andrea Paternesi
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: NetbeansError.png, test-gradle-netbeans.tgz
>
>
> When the project tries to reload dependencies for some strange reason it 
> stops and never download any file.
> You are forced to open a shell and  force the reload of dependencies by hand 
> using "./gradlew clean build".
> After that you can "clean and build" also in netbeans and then the project 
> returns to compile without problems.
> This bug coupled with this one 
> https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
> very hard to use with gradle.
> Thanks for any patch you can provide.
>  



--
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] [Updated] (NETBEANS-3385) Reload of dependencies in a gradle project always fails.

2019-11-23 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi updated NETBEANS-3385:
---
Attachment: NetbeansError.png

> Reload of dependencies in a gradle project always fails.
> 
>
> Key: NETBEANS-3385
> URL: https://issues.apache.org/jira/browse/NETBEANS-3385
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: Andrea Paternesi
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: NetbeansError.png, test-gradle-netbeans.tgz
>
>
> When the project tries to reload dependencies for some strange reason it 
> stops and never download any file.
> You are forced to open a shell and  force the reload of dependencies by hand 
> using "./gradlew clean build".
> After that you can "clean and build" also in netbeans and then the project 
> returns to compile without problems.
> This bug coupled with this one 
> https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
> very hard to use with gradle.
> Thanks for any patch you can provide.
>  



--
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-3385) Reload of dependencies in a gradle project always fails.

2019-11-22 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi commented on NETBEANS-3385:


Excuse me whare do I find the IDE log? I am using linux.

> Reload of dependencies in a gradle project always fails.
> 
>
> Key: NETBEANS-3385
> URL: https://issues.apache.org/jira/browse/NETBEANS-3385
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: Andrea Paternesi
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: test-gradle-netbeans.tgz
>
>
> When the project tries to reload dependencies for some strange reason it 
> stops and never download any file.
> You are forced to open a shell and  force the reload of dependencies by hand 
> using "./gradlew clean build".
> After that you can "clean and build" also in netbeans and then the project 
> returns to compile without problems.
> This bug coupled with this one 
> https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
> very hard to use with gradle.
> Thanks for any patch you can provide.
>  



--
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] [Comment Edited] (NETBEANS-3385) Reload of dependencies in a gradle project always fails.

2019-11-22 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi edited comment on NETBEANS-3385 at 11/22/19 8:09 AM:
--

Excuse me where do I find the IDE log? I am using linux.


was (Author: patton73):
Excuse me whare do I find the IDE log? I am using linux.

> Reload of dependencies in a gradle project always fails.
> 
>
> Key: NETBEANS-3385
> URL: https://issues.apache.org/jira/browse/NETBEANS-3385
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: Andrea Paternesi
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: test-gradle-netbeans.tgz
>
>
> When the project tries to reload dependencies for some strange reason it 
> stops and never download any file.
> You are forced to open a shell and  force the reload of dependencies by hand 
> using "./gradlew clean build".
> After that you can "clean and build" also in netbeans and then the project 
> returns to compile without problems.
> This bug coupled with this one 
> https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
> very hard to use with gradle.
> Thanks for any patch you can provide.
>  



--
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] [Comment Edited] (NETBEANS-3385) Reload of dependencies in a gradle project always fails.

2019-11-20 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi edited comment on NETBEANS-3385 at 11/20/19 8:50 AM:
--

More:

if you set back the old dependency from 3.6.0 to 3.5.0. The project will not 
compile anymore. Since it will not download the old dependency and the errors 
will not go away anymore (even if you try to clean and build). You are forced 
to open a shell and force the dependency download by hand using gradle.

 


was (Author: patton73):
More:

if you set back the old dependency from 3.6.0 to 3.5.0. The project will not 
compile anymore. Since it will not download the old dependency and the errors 
will not go away anymore. You are forced to open a shell and force the 
dependency download by hand using gradle.

 

> Reload of dependencies in a gradle project always fails.
> 
>
> Key: NETBEANS-3385
> URL: https://issues.apache.org/jira/browse/NETBEANS-3385
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: Andrea Paternesi
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: test-gradle-netbeans.tgz
>
>
> When the project tries to reload dependencies for some strange reason it 
> stops and never download any file.
> You are forced to open a shell and  force the reload of dependencies by hand 
> using "./gradlew clean build".
> After that you can "clean and build" also in netbeans and then the project 
> returns to compile without problems.
> This bug coupled with this one 
> https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
> very hard to use with gradle.
> Thanks for any patch you can provide.
>  



--
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-3385) Reload of dependencies in a gradle project always fails.

2019-11-20 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi commented on NETBEANS-3385:


More:

if you set back the old dependency from 3.6.0 to 3.5.0. The project will not 
compile anymore. Since it will not download the old dependency and the errors 
will not go away anymore. You are forced to open a shell and force the 
dependency download by hand using gradle.

 

> Reload of dependencies in a gradle project always fails.
> 
>
> Key: NETBEANS-3385
> URL: https://issues.apache.org/jira/browse/NETBEANS-3385
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: Andrea Paternesi
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: test-gradle-netbeans.tgz
>
>
> When the project tries to reload dependencies for some strange reason it 
> stops and never download any file.
> You are forced to open a shell and  force the reload of dependencies by hand 
> using "./gradlew clean build".
> After that you can "clean and build" also in netbeans and then the project 
> returns to compile without problems.
> This bug coupled with this one 
> https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
> very hard to use with gradle.
> Thanks for any patch you can provide.
>  



--
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-3385) Reload of dependencies in a gradle project always fails.

2019-11-18 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi commented on NETBEANS-3385:


Hi,

I have provided a mini project as a test for this bug. 
[^test-gradle-netbeans.tgz]

Basically just open it with netbeans 11.2 then wait for project initialization.

After that just modify the build.gradle in the dependencies settings using 
javalin 3.6.0 version instead of javalin 3.5.0.

The dependency won't be downloaded and an error occurs. It happens always.

Hope you can reporduce the error.

Thanks.

> Reload of dependencies in a gradle project always fails.
> 
>
> Key: NETBEANS-3385
> URL: https://issues.apache.org/jira/browse/NETBEANS-3385
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: Andrea Paternesi
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: test-gradle-netbeans.tgz
>
>
> When the project tries to reload dependencies for some strange reason it 
> stops and never download any file.
> You are forced to open a shell and  force the reload of dependencies by hand 
> using "./gradlew clean build".
> After that you can "clean and build" also in netbeans and then the project 
> returns to compile without problems.
> This bug coupled with this one 
> https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
> very hard to use with gradle.
> Thanks for any patch you can provide.
>  



--
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] [Updated] (NETBEANS-3385) Reload of dependencies in a gradle project always fails.

2019-11-18 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi updated NETBEANS-3385:
---
Attachment: test-gradle-netbeans.tgz

> Reload of dependencies in a gradle project always fails.
> 
>
> Key: NETBEANS-3385
> URL: https://issues.apache.org/jira/browse/NETBEANS-3385
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.2
>Reporter: Andrea Paternesi
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: test-gradle-netbeans.tgz
>
>
> When the project tries to reload dependencies for some strange reason it 
> stops and never download any file.
> You are forced to open a shell and  force the reload of dependencies by hand 
> using "./gradlew clean build".
> After that you can "clean and build" also in netbeans and then the project 
> returns to compile without problems.
> This bug coupled with this one 
> https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
> very hard to use with gradle.
> Thanks for any patch you can provide.
>  



--
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] [Updated] (NETBEANS-3385) Reload of dependencies in a gradle project always fails.

2019-11-14 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi updated NETBEANS-3385:
---
Description: 
When the project tries to reload dependencies for some strange reason it stops 
and never download any file.

You are forced to open a shell and  force the reload of dependencies by hand 
using "./gradlew clean build".

After that you can "clean and build" also in netbeans and then the project 
returns to compile without problems.

This bug coupled with this one 
https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
very hard to use with gradle.

Thanks for any patch you can provide.

 

  was:
When the project tries to reload dependencies for some strange reason it stops 
and never download any file.

You are forced to open a shell, force the reload of dependencies by hand

using "./gradlew clean build".

After that you can "clean and build" also in netbeans and then the project 
returns to compile without problems.

This bug coupled with this one 
https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
very hard to use with gradle.

Thanks for any patch you can provide.

 


> Reload of dependencies in a gradle project always fails.
> 
>
> Key: NETBEANS-3385
> URL: https://issues.apache.org/jira/browse/NETBEANS-3385
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.2
>Reporter: Andrea Paternesi
>Priority: Major
>
> When the project tries to reload dependencies for some strange reason it 
> stops and never download any file.
> You are forced to open a shell and  force the reload of dependencies by hand 
> using "./gradlew clean build".
> After that you can "clean and build" also in netbeans and then the project 
> returns to compile without problems.
> This bug coupled with this one 
> https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
> very hard to use with gradle.
> Thanks for any patch you can provide.
>  



--
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] [Comment Edited] (NETBEANS-2960) Need a force reload action for Gradle projects

2019-11-14 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi edited comment on NETBEANS-2960 at 11/14/19 8:23 AM:
--

This lack of feature is really annoying. Right now the only way to force a 
project reload is to put a blank space into build.gradle and save the file.

This should be implemented as it is now is a waste of time.

Thanks.


was (Author: patton73):
This lack of feature is real annoying. Right now the only way to force a 
project reload is to put a blank space into build.gradle and save the file.

This should be implemented as it is now is a waste of time.

Thanks.

> Need a force reload action for Gradle projects
> --
>
> Key: NETBEANS-2960
> URL: https://issues.apache.org/jira/browse/NETBEANS-2960
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0, 11.1, 11.2
>Reporter: Travis
>Assignee: Laszlo Kishalmi
>Priority: Minor
>
> I have a multi-project gradle build with a settings.gradle implementation 
> that auto-detects the subprojects.  So whenever a subproject gets 
> added/removed/renamed (either directly, or as the result of a git branch 
> checkout), the root project build.gradle and settings.gradle do not need to 
> be modified at all.
> Currently, the gradle support assumes that projects only need to be reloaded 
> when build.gradle or settings.gradle change, but my build breaks this 
> assumption.
> So the behavior in my case is that I am not even able to manually browse to a 
> new subproject and open it, until after I make a meaningless edit to 
> build.gradle or settings.gradle.  The new subproject folder is not even 
> recognized as a gradle project in the "open project" dialog until I have 
> touched one of those files.
> This behavior is broken.  Ideally, projects that come and go would 
> automatically get noticed, and the IDE would update immediately.  But 
> assuming that's non-trivial to implement, it would be acceptable to simply 
> add a manually-triggerable "force project reload" action somewhere in the 
> GUI, so that the user can get back into a good state without the need to 
> touch any files.
>  
> Thanks!



--
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] [Comment Edited] (NETBEANS-2960) Need a force reload action for Gradle projects

2019-11-14 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi edited comment on NETBEANS-2960 at 11/14/19 8:22 AM:
--

This lack of feature is real annoying. Right now the only way to force a 
project reload is to put a blank space into build.gradle and save the file.

This should be implemented as it is now is a waste of time.

Thanks.


was (Author: patton73):
This lack of feature is real annoying. Right now the only way to force a 
project reload is to put a blanck space into build.gradle and save the file.

This should be implemented as it is now is a waste of time.

Thanks.

> Need a force reload action for Gradle projects
> --
>
> Key: NETBEANS-2960
> URL: https://issues.apache.org/jira/browse/NETBEANS-2960
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0, 11.1, 11.2
>Reporter: Travis
>Assignee: Laszlo Kishalmi
>Priority: Minor
>
> I have a multi-project gradle build with a settings.gradle implementation 
> that auto-detects the subprojects.  So whenever a subproject gets 
> added/removed/renamed (either directly, or as the result of a git branch 
> checkout), the root project build.gradle and settings.gradle do not need to 
> be modified at all.
> Currently, the gradle support assumes that projects only need to be reloaded 
> when build.gradle or settings.gradle change, but my build breaks this 
> assumption.
> So the behavior in my case is that I am not even able to manually browse to a 
> new subproject and open it, until after I make a meaningless edit to 
> build.gradle or settings.gradle.  The new subproject folder is not even 
> recognized as a gradle project in the "open project" dialog until I have 
> touched one of those files.
> This behavior is broken.  Ideally, projects that come and go would 
> automatically get noticed, and the IDE would update immediately.  But 
> assuming that's non-trivial to implement, it would be acceptable to simply 
> add a manually-triggerable "force project reload" action somewhere in the 
> GUI, so that the user can get back into a good state without the need to 
> touch any files.
>  
> Thanks!



--
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] [Updated] (NETBEANS-3385) Reload of dependencies in a gradle project always fails.

2019-11-14 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi updated NETBEANS-3385:
---
Description: 
When the project tries to reload dependencies for some strange reason it stops 
and never download any file.

You are forced to open a shell, force the reload of dependencies by hand

using "./gradlew clean build".

After that you can "clean and build" also in netbeans and then the project 
returns to compile without problems.

This bug coupled with this one 
https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
very hard to use with gradle.

Thanks for any patch you can provide.

 

  was:
When the project tries to reload dependencies for some strange reason it stops 
and never download any file.

You are forced to open a shell, force the reload of dependencies by hand 

using "./gradlew clean build".

After that you can "clean and build" also in netbeans and then the project 
returns to compile without problems.

This bug coupled with this one 
https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
vary hard to use with gradle.

Thanks for any patch you can provide.

 


> Reload of dependencies in a gradle project always fails.
> 
>
> Key: NETBEANS-3385
> URL: https://issues.apache.org/jira/browse/NETBEANS-3385
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.2
>Reporter: Andrea Paternesi
>Priority: Major
>
> When the project tries to reload dependencies for some strange reason it 
> stops and never download any file.
> You are forced to open a shell, force the reload of dependencies by hand
> using "./gradlew clean build".
> After that you can "clean and build" also in netbeans and then the project 
> returns to compile without problems.
> This bug coupled with this one 
> https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
> very hard to use with gradle.
> Thanks for any patch you can provide.
>  



--
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] [Created] (NETBEANS-3385) Reload of dependencies in a gradle project always fails.

2019-11-14 Thread Andrea Paternesi (Jira)
Andrea Paternesi created NETBEANS-3385:
--

 Summary: Reload of dependencies in a gradle project always fails.
 Key: NETBEANS-3385
 URL: https://issues.apache.org/jira/browse/NETBEANS-3385
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 11.2
Reporter: Andrea Paternesi


When the project tries to reload dependencies for some strange reason it stops 
and never download any file.

You are forced to open a shell, force the reload of dependencies by hand 

using "./gradlew clean build".

After that you can "clean and build" also in netbeans and then the project 
returns to compile without problems.

This bug coupled with this one 
https://issues.apache.org/jira/browse/NETBEANS-2960 makes the ide basically 
vary hard to use with gradle.

Thanks for any patch you can provide.

 



--
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] [Updated] (NETBEANS-2960) Need a force reload action for Gradle projects

2019-11-14 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi updated NETBEANS-2960:
---
Affects Version/s: 11.2

> Need a force reload action for Gradle projects
> --
>
> Key: NETBEANS-2960
> URL: https://issues.apache.org/jira/browse/NETBEANS-2960
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0, 11.1, 11.2
>Reporter: Travis
>Assignee: Laszlo Kishalmi
>Priority: Minor
>
> I have a multi-project gradle build with a settings.gradle implementation 
> that auto-detects the subprojects.  So whenever a subproject gets 
> added/removed/renamed (either directly, or as the result of a git branch 
> checkout), the root project build.gradle and settings.gradle do not need to 
> be modified at all.
> Currently, the gradle support assumes that projects only need to be reloaded 
> when build.gradle or settings.gradle change, but my build breaks this 
> assumption.
> So the behavior in my case is that I am not even able to manually browse to a 
> new subproject and open it, until after I make a meaningless edit to 
> build.gradle or settings.gradle.  The new subproject folder is not even 
> recognized as a gradle project in the "open project" dialog until I have 
> touched one of those files.
> This behavior is broken.  Ideally, projects that come and go would 
> automatically get noticed, and the IDE would update immediately.  But 
> assuming that's non-trivial to implement, it would be acceptable to simply 
> add a manually-triggerable "force project reload" action somewhere in the 
> GUI, so that the user can get back into a good state without the need to 
> touch any files.
>  
> Thanks!



--
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-2960) Need a force reload action for Gradle projects

2019-11-14 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi commented on NETBEANS-2960:


This lack of feature is real annoying. Right now the only way to force a 
project reload is to put a blanck space into build.gradle and save the file.

This should be implemented as it is now is a waste of time.

Thanks.

> Need a force reload action for Gradle projects
> --
>
> Key: NETBEANS-2960
> URL: https://issues.apache.org/jira/browse/NETBEANS-2960
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0, 11.1, 11.2
>Reporter: Travis
>Assignee: Laszlo Kishalmi
>Priority: Minor
>
> I have a multi-project gradle build with a settings.gradle implementation 
> that auto-detects the subprojects.  So whenever a subproject gets 
> added/removed/renamed (either directly, or as the result of a git branch 
> checkout), the root project build.gradle and settings.gradle do not need to 
> be modified at all.
> Currently, the gradle support assumes that projects only need to be reloaded 
> when build.gradle or settings.gradle change, but my build breaks this 
> assumption.
> So the behavior in my case is that I am not even able to manually browse to a 
> new subproject and open it, until after I make a meaningless edit to 
> build.gradle or settings.gradle.  The new subproject folder is not even 
> recognized as a gradle project in the "open project" dialog until I have 
> touched one of those files.
> This behavior is broken.  Ideally, projects that come and go would 
> automatically get noticed, and the IDE would update immediately.  But 
> assuming that's non-trivial to implement, it would be acceptable to simply 
> add a manually-triggerable "force project reload" action somewhere in the 
> GUI, so that the user can get back into a good state without the need to 
> touch any files.
>  
> Thanks!



--
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] [Created] (NETBEANS-3327) Netbeans 11.2 gradle multi project resource issue

2019-11-01 Thread Andrea Paternesi (Jira)
Andrea Paternesi created NETBEANS-3327:
--

 Summary: Netbeans 11.2 gradle multi project resource issue
 Key: NETBEANS-3327
 URL: https://issues.apache.org/jira/browse/NETBEANS-3327
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 11.2
Reporter: Andrea Paternesi
 Attachments: netbeans11.2-gradle-error.png

*I am using latest java 8 version and gradle 5.6.3 wrapper in both netbeans 8.2 
and 11.2*

If you have a multiproject configuration similar to this:

parent Project -> sub project 1, sub project2

And subproject 2 resources are bounded to a sub project 1 directory,

*+sub project 2 won't find resources+*.

It works correctly in netbeans 8.2 (same configuration). And it does not depend 
from gradle version since i used latest (5.6.3) in both IDEs.

I attach a picture of what IDE says about error.

You can see from the picture that "*sourceSets.main.resources.srcDirs*" command 
cause the error in the project "*Error Node: Resources ...*"

Do you have any clue? Is there a place i can see the stacktrace of the problem 
in the ide?

Thank a lot.

Andrea.



--
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] [Comment Edited] (NETBEANS-2555) When running any test, standard output is not shown in the panel to the right of the test file result.

2019-08-27 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi edited comment on NETBEANS-2555 at 8/27/19 6:28 AM:
-

This is a bug to me not an improvement. Old plugin had it. And if we canno see 
tests output in netbeans consolle is a real problem.

We are stuck with netbeans 10 version since test output are not shown anymore.

More if with gradle we use interactive commands, now we cannot launch tasks 
anymore because the interactive output is not shown in the consolle and gradle 
does not accept user input.


was (Author: patton73):
This is a bug to me not an improvement. Old pluging had it. And if we canno see 
tests output in netbeans consolle is a real problem.

We are stuck with netbeans 10 version since test output are not shown anymore.

More if with gradle we use interactive commands, now we cannot launch tasks 
anymore because the interactive output is not shown in the consolle

and gradle does not accept user input.

> When running any test, standard output is not shown in the panel to the right 
> of the test file result.
> --
>
> Key: NETBEANS-2555
> URL: https://issues.apache.org/jira/browse/NETBEANS-2555
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Affects Versions: 11.0, 11.1
>Reporter: Mark Flacy
>Assignee: Laszlo Kishalmi
>Priority: Minor
>
> It isn't important that the output is available on the side panel while the 
> test is running; it is sufficient to me if the output is presented after the 
> tests have run if I select a specific test on the test panel.
> I have a simple project at github that shows the behavior.
> [https://github.com/Richard-Cranium/NB11GradleJunitExample]
> The head of the master branch is the gradle based project that shows the 
> misleading behavior.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
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-2555) When running any test, standard output is not shown in the panel to the right of the test file result.

2019-08-26 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi commented on NETBEANS-2555:


This is a bug to me not an improvement. Old pluging had it. And if we canno see 
tests output in netbeans consolle is a real problem.

We are stuck with netbeans 10 version since test output are not shown anymore.

More if with gradle we use interactive commands, now we cannot launch tasks 
anymore because the interactive output is not shown in the consolle

and gradle does not accept user input.

> When running any test, standard output is not shown in the panel to the right 
> of the test file result.
> --
>
> Key: NETBEANS-2555
> URL: https://issues.apache.org/jira/browse/NETBEANS-2555
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Affects Versions: 11.0, 11.1
>Reporter: Mark Flacy
>Assignee: Laszlo Kishalmi
>Priority: Minor
>
> It isn't important that the output is available on the side panel while the 
> test is running; it is sufficient to me if the output is presented after the 
> tests have run if I select a specific test on the test panel.
> I have a simple project at github that shows the behavior.
> [https://github.com/Richard-Cranium/NB11GradleJunitExample]
> The head of the master branch is the gradle based project that shows the 
> misleading behavior.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
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-2960) Need a force reload action for Gradle projects

2019-08-26 Thread Andrea Paternesi (Jira)


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

Andrea Paternesi commented on NETBEANS-2960:


This is really needed. The old plugin had it.

Thank you very much.

> Need a force reload action for Gradle projects
> --
>
> Key: NETBEANS-2960
> URL: https://issues.apache.org/jira/browse/NETBEANS-2960
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0, 11.1
>Reporter: Travis
>Assignee: Laszlo Kishalmi
>Priority: Minor
>
> I have a multi-project gradle build with a settings.gradle implementation 
> that auto-detects the subprojects.  So whenever a subproject gets 
> added/removed/renamed (either directly, or as the result of a git branch 
> checkout), the root project build.gradle and settings.gradle do not need to 
> be modified at all.
> Currently, the gradle support assumes that projects only need to be reloaded 
> when build.gradle or settings.gradle change, but my build breaks this 
> assumption.
> So the behavior in my case is that I am not even able to manually browse to a 
> new subproject and open it, until after I make a meaningless edit to 
> build.gradle or settings.gradle.  The new subproject folder is not even 
> recognized as a gradle project in the "open project" dialog until I have 
> touched one of those files.
> This behavior is broken.  Ideally, projects that come and go would 
> automatically get noticed, and the IDE would update immediately.  But 
> assuming that's non-trivial to implement, it would be acceptable to simply 
> add a manually-triggerable "force project reload" action somewhere in the 
> GUI, so that the user can get back into a good state without the need to 
> touch any files.
>  
> Thanks!



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
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-2550) NetBeans 11 does not show Gradle junit output

2019-05-15 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi commented on NETBEANS-2550:


Just create an unit test with inside a system out. And run the test. No output 
will be shown.

> NetBeans 11 does not show Gradle junit output
> -
>
> Key: NETBEANS-2550
> URL: https://issues.apache.org/jira/browse/NETBEANS-2550
> Project: NetBeans
>  Issue Type: Bug
>  Components: gradle, projects - Gradle
>Affects Versions: 11.0
>Reporter: Andrea Paternesi
>Priority: Major
>
> When launching test (Junit) Netbeans does not show any output. It does not 
> show either the System.out.println() nor the Log output in the consolle.
> This is a serious problem.



--
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-2550) Netbeans 11 does not show junit output

2019-05-15 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi commented on NETBEANS-2550:


I am using Junit test with new gradle support.

> Netbeans 11 does not show junit output
> --
>
> Key: NETBEANS-2550
> URL: https://issues.apache.org/jira/browse/NETBEANS-2550
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.0
>Reporter: Andrea Paternesi
>Priority: Major
>
> When launching test (Junit) Netbeans does not show any output. It does not 
> show either the System.out.println() nor the Log output in the consolle.
> This is a serious problem.



--
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] [Updated] (NETBEANS-2550) Netbeans 11 does not show junit output

2019-05-15 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi updated NETBEANS-2550:
---
Description: 
When launching test (Junit) Netbeans does not show any output. It does not show 
either the System.out.println() nor the Log output in the consolle.

This is a serious problem.

  was:
When launching test Netbeans does not show any output. It does not show either 
the System.out.println() nor the Log output in the consolle.

This is a serious problem.


> Netbeans 11 does not show junit output
> --
>
> Key: NETBEANS-2550
> URL: https://issues.apache.org/jira/browse/NETBEANS-2550
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.0
>Reporter: Andrea Paternesi
>Priority: Major
>
> When launching test (Junit) Netbeans does not show any output. It does not 
> show either the System.out.println() nor the Log output in the consolle.
> This is a serious problem.



--
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] [Updated] (NETBEANS-2550) Netbeans 11 does not show junit output

2019-05-15 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi updated NETBEANS-2550:
---
Description: 
When launching test Netbeans does not show any output. It does not show either 
the System.out.println() nor the Log output in the consolle.

This is a serious problem.

  was:
When launching test Netbeans does not show any output. It does not show either 
the System.out.println() nor the Log output in the consolle.

This is problem.


> Netbeans 11 does not show junit output
> --
>
> Key: NETBEANS-2550
> URL: https://issues.apache.org/jira/browse/NETBEANS-2550
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.0
>Reporter: Andrea Paternesi
>Priority: Major
>
> When launching test Netbeans does not show any output. It does not show 
> either the System.out.println() nor the Log output in the consolle.
> This is a serious problem.



--
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] [Created] (NETBEANS-2550) Netbeans 11 does not show junit output

2019-05-15 Thread Andrea Paternesi (JIRA)
Andrea Paternesi created NETBEANS-2550:
--

 Summary: Netbeans 11 does not show junit output
 Key: NETBEANS-2550
 URL: https://issues.apache.org/jira/browse/NETBEANS-2550
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 11.0
Reporter: Andrea Paternesi


When launching test Netbeans does not show any output. It does not show either 
the System.out.println() nor the Log output in the consolle.

This is problem.



--
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-939) MEMORY LEAK!!

2019-05-15 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi commented on NETBEANS-939:
---

After some months of usage the bug is still there. Usually happens when i leave 
the keyboard for some time. When i log in again Netbeans is blocked with the 
heap full of garbage. But no heap dump. only full memory and ide basically 
blocked. I set the heap space do 2GB and it fills it up always.

Could not try netbeans 11 because gradle support has too many bugs and it is 
almost unusable to me with my gradle projects. More it lacks the most important 
feature of the old plugin: reload project.

I will opne new bugs for that.

 

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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-939) MEMORY LEAK!!

2019-01-10 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi commented on NETBEANS-939:
---

It is likely to be related to the gradle plugin. After 8 hours the empty 
netbeans did not crash.

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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] [Comment Edited] (NETBEANS-939) MEMORY LEAK!!

2019-01-10 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi edited comment on NETBEANS-939 at 1/10/19 8:05 AM:


Ah ok i will test this. I just open another netbeans with no project opened and 
see if the memory still grows.


was (Author: patton73):
Ah ok i will test this. I just open anothe netbeans with no project opened and 
see if the memory still grows.

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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-939) MEMORY LEAK!!

2019-01-10 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi commented on NETBEANS-939:
---

Ah ok i will test this. I just open anothe netbeans with no project opened and 
see if the memory still grows.

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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] [Comment Edited] (NETBEANS-939) MEMORY LEAK!!

2019-01-10 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi edited comment on NETBEANS-939 at 1/10/19 8:02 AM:


The gradle daemons usually run in different processes.

this is the output of the ps -aux | grep java

patton 3923 1.2 1.4 5631888 470796 ? Ssl 08:25 0:22 
/usr/lib/jvm/java-8-oracle/bin/java -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m 
-Dfile.encoding=UTF-8 -Duser.country=IT -Duser.language=it -Duser.variant -cp 
/home/patton/.gradle/wrapper/dists/gradle-4.9-bin/e9cinqnqvph59rr7g70qubb4t/gradle-4.9/lib/gradle-launcher-4.9.jar
 org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.9

As you can see i have a different process for the gradle daemon.

Anyway i try to reproduce it opening one project per time.

 

Ah i forgot to say that i have a 32GB powerful workstation. So lack of memory 
is not the problem.

 


was (Author: patton73):
The gradle daemons usually run in different processes.

this is the output of the ps -aux | grep java

patton 3923 1.2 1.4 5631888 470796 ? Ssl 08:25 0:22 
/usr/lib/jvm/java-8-oracle/bin/java -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m 
-Dfile.encoding=UTF-8 -Duser.country=IT -Duser.language=it -Duser.variant -cp 
/home/patton/.gradle/wrapper/dists/gradle-4.9-bin/e9cinqnqvph59rr7g70qubb4t/gradle-4.9/lib/gradle-launcher-4.9.jar
 org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.9

As you can see i have a different process for the gradle daemon.

Anyway i try to reproduce it opening one project per time.

 

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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] [Comment Edited] (NETBEANS-939) MEMORY LEAK!!

2019-01-10 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi edited comment on NETBEANS-939 at 1/10/19 8:00 AM:


The gradle daemons usually run in different processes.

this is the output of the ps -aux | grep java

patton 3923 1.2 1.4 5631888 470796 ? Ssl 08:25 0:22 
/usr/lib/jvm/java-8-oracle/bin/java -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m 
-Dfile.encoding=UTF-8 -Duser.country=IT -Duser.language=it -Duser.variant -cp 
/home/patton/.gradle/wrapper/dists/gradle-4.9-bin/e9cinqnqvph59rr7g70qubb4t/gradle-4.9/lib/gradle-launcher-4.9.jar
 org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.9

As you can see i have a different process for the gradle daemon.

Anyway i try to reproduce it opening one project per time.

 


was (Author: patton73):
The gradle daemons usually run in different processes.

this is the output of the ps -aux | grep java

patton 3923 1.2 1.4 5631888 470796 ? Ssl 08:25 0:22 
/usr/lib/jvm/java-8-oracle/bin/java -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m 
-Dfile.encoding=UTF-8 -Duser.country=IT -Duser.language=it -Duser.variant -cp 
/home/patton/.gradle/wrapper/dists/gradle-4.9-bin/e9cinqnqvph59rr7g70qubb4t/gradle-4.9/lib/gradle-launcher-4.9.jar
 org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.9

As you can see i have a different process for the gradle daemon.

 

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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] [Comment Edited] (NETBEANS-939) MEMORY LEAK!!

2019-01-10 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi edited comment on NETBEANS-939 at 1/10/19 7:59 AM:


The gradle daemons usually run in different processes.

this is the output of the ps -aux | grep java

atton 3923 1.2 1.4 5631888 470796 ? Ssl 08:25 0:22 
/usr/lib/jvm/java-8-oracle/bin/java -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m 
-Dfile.encoding=UTF-8 -Duser.country=IT -Duser.language=it -Duser.variant -cp 
/home/patton/.gradle/wrapper/dists/gradle-4.9-bin/e9cinqnqvph59rr7g70qubb4t/gradle-4.9/lib/gradle-launcher-4.9.jar
 org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.9

As you can see i have a different process for the gradle daemon.

 


was (Author: patton73):
The gradle daemons usually run in different processes.

this is the utput of the ps -aux | grep java

atton 3923 1.2 1.4 5631888 470796 ? Ssl 08:25 0:22 
/usr/lib/jvm/java-8-oracle/bin/java -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m 
-Dfile.encoding=UTF-8 -Duser.country=IT -Duser.language=it -Duser.variant -cp 
/home/patton/.gradle/wrapper/dists/gradle-4.9-bin/e9cinqnqvph59rr7g70qubb4t/gradle-4.9/lib/gradle-launcher-4.9.jar
 org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.9

As you can see i have a different process for the gradle daemon.

 

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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] [Comment Edited] (NETBEANS-939) MEMORY LEAK!!

2019-01-10 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi edited comment on NETBEANS-939 at 1/10/19 7:59 AM:


The gradle daemons usually run in different processes.

this is the output of the ps -aux | grep java

patton 3923 1.2 1.4 5631888 470796 ? Ssl 08:25 0:22 
/usr/lib/jvm/java-8-oracle/bin/java -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m 
-Dfile.encoding=UTF-8 -Duser.country=IT -Duser.language=it -Duser.variant -cp 
/home/patton/.gradle/wrapper/dists/gradle-4.9-bin/e9cinqnqvph59rr7g70qubb4t/gradle-4.9/lib/gradle-launcher-4.9.jar
 org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.9

As you can see i have a different process for the gradle daemon.

 


was (Author: patton73):
The gradle daemons usually run in different processes.

this is the output of the ps -aux | grep java

atton 3923 1.2 1.4 5631888 470796 ? Ssl 08:25 0:22 
/usr/lib/jvm/java-8-oracle/bin/java -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m 
-Dfile.encoding=UTF-8 -Duser.country=IT -Duser.language=it -Duser.variant -cp 
/home/patton/.gradle/wrapper/dists/gradle-4.9-bin/e9cinqnqvph59rr7g70qubb4t/gradle-4.9/lib/gradle-launcher-4.9.jar
 org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.9

As you can see i have a different process for the gradle daemon.

 

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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-939) MEMORY LEAK!!

2019-01-10 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi commented on NETBEANS-939:
---

The gradle daemons usually run in different processes.

this is the utput of the ps -aux | grep java

atton 3923 1.2 1.4 5631888 470796 ? Ssl 08:25 0:22 
/usr/lib/jvm/java-8-oracle/bin/java -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m 
-Dfile.encoding=UTF-8 -Duser.country=IT -Duser.language=it -Duser.variant -cp 
/home/patton/.gradle/wrapper/dists/gradle-4.9-bin/e9cinqnqvph59rr7g70qubb4t/gradle-4.9/lib/gradle-launcher-4.9.jar
 org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.9

As you can see i have a different process for the gradle daemon.

 

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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] [Comment Edited] (NETBEANS-939) MEMORY LEAK!!

2019-01-09 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi edited comment on NETBEANS-939 at 1/10/19 7:55 AM:


Well according to my experience this leak can be reproduced also in netbeans 9 
and 10.

What happens to me is that basically without doing anything the memory usage 
simply grows up. I had to set an Xmx setting of 2GB of memory to mitigate the 
problem but if i leave the computer idle with netbeans opened usually i find 
the ide blocked with all the 2GB of memory used. Then the ide becomes unusable 
and i have to kill it from shell.

I use Linux. I really can't reproduce the bug but it simply happens to me 
always. It is just a matter of time elapsed from the start. I can add that i 
have usually opened about 20 gradle projects. More when this happens no logs or 
heap errors on the shell are issued from netbeans.

java version "1.8.0_191"
Java(TM) SE Runtime Environment (build 1.8.0_191-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)

Linux 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

 

 

 


was (Author: patton73):
Well according to my experience this leak can be reproduced also in netbeans 9 
and 10.

What happens to me is that basically without doing anything the memory usage 
simply grows up. I had to set an Xmx setting of 2GB of memory to mitigate the 
problem but if i leave the computer idle with netbeans opened usually i find 
the ide blocked with all the 2GB of memory used. Then the ide becomes unusable 
and i have to kill it from shell.

I use Linux. I really can't reproduce the bug but it simply happens to me 
always. It is just a matter of time elapsed from the start. I can add that i 
have usually opened about 20 gradle projects. More when this happens no logs or 
heap errors on the shell are issued from netbeans.

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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] [Comment Edited] (NETBEANS-939) MEMORY LEAK!!

2019-01-09 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi edited comment on NETBEANS-939 at 1/10/19 7:44 AM:


Well according to my experience this leak can be reproduced also in netbeans 9 
and 10.

What happens to me is that basically without doing anything the memory usage 
simply grows up. I had to set an Xmx setting of 2GB of memory to mitigate the 
problem but if i leave the computer idle with netbeans opened usually i find 
the ide blocked with all the 2GB of memory used. Then the ide becomes unusable 
and i have to kill it from shell.

I use Linux. I really can't reproduce the bug but it simply happens to me 
always. It is just a matter of time elapsed from the start. I can add that i 
have usually opened about 20 gradle projects. More when this happens no logs or 
heap errors on the shell are issued from netbeans.


was (Author: patton73):
Well according to my experience this leak can be reproduced also in netbeans 9 
and 10.

What happens to me is that basically without doing anything the memory usage 
simply grows up. I had to set an Xmx setting of 2GB of memory to mitigate the 
problem but if i leave the computer idle with netbeans opened usually i find 
the ide blocked with all the 2GB of memory used. Then the ide becomes unusable 
and i have to kill it from shell.

I use Linux. I really can't reproduce the bug but it simply happens to me 
always. It is just a matter of time elapsed from the start. I can add that i 
have usually opened about 20 gradle projects.

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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] [Comment Edited] (NETBEANS-939) MEMORY LEAK!!

2019-01-09 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi edited comment on NETBEANS-939 at 1/10/19 7:43 AM:


Well according to my experience this leak can be reproduced also in netbeans 9 
and 10.

What happens to me is that basically without doing anything the memory usage 
simply grows up. I had to set an Xmx setting of 2GB of memory to mitigate the 
problem but if i leave the computer idle with netbeans opened usually i find 
the ide blocked with all the 2GB of memory used. Then the ide becomes unusable 
and i have to kill it from shell.

I use Linux. I really can't reproduce the bug but it simply happens to me 
always. It is just a matter of time elapsed from the start. I can add that i 
have usually opened about 20 gradle projects.


was (Author: patton73):
Well according to my experience this leak can be reproduced also in netbeans 9 
and 10.

What happens to me is that basically without doing anything the memory usage 
simply grows up. I had to se an Xmx setting of 2GB of memory to mitigate the 
problem but if i leave the computer idle with netbeans opened usually i find 
the ide blocked with all the 2GB of memory used. Then the ide becomes unusable 
and i have to kill it from shell.

I use Linux. I really can't reproduce the bug but it simply happens to me 
always. It is just a matter of time elapsed from the start. I can add that i 
have usually opened about 20 gradle projects.

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



--
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-939) MEMORY LEAK!!

2019-01-09 Thread Andrea Paternesi (JIRA)


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

Andrea Paternesi commented on NETBEANS-939:
---

Well according to my experience this leak can be reproduced also in netbeans 9 
and 10.

What happens to me is that basically without doing anything the memory usage 
simply grows up. I had to se an Xmx setting of 2GB of memory to mitigate the 
problem but if i leave the computer idle with netbeans opened usually i find 
the ide blocked with all the 2GB of memory used. Then the ide becomes unusable 
and i have to kill it from shell.

I use Linux. I really can't reproduce the bug but it simply happens to me 
always. It is just a matter of time elapsed from the start. I can add that i 
have usually opened about 20 gradle projects.

> MEMORY LEAK!!
> -
>
> Key: NETBEANS-939
> URL: https://issues.apache.org/jira/browse/NETBEANS-939
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Performance
>Affects Versions: 8.2
> Environment: See above
>Reporter: Andrew Hellyer
>Priority: Major
>
> *Product Version:* NetBeans IDE 8.2 (Build 201705191307)
> *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 
> 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo]
> *Java:* 1.8.0_172; Java HotSpot(TM) 64-Bit Server VM 25.172-b11
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_172-b11
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
>  
>  
> *I have multiple projects open with multiple files from each open.*
> *Simply moving from file to file or moving the mouse increases memory usage.*
> *This just gets progressively worse as time goes on, until NB is so slow it 
> has to be restarted or the computer crashes/freezes due to memory issues.* 
> ***This has been happening since 8.2 came out. How come nobody has done 
> anything about it? There are multiple reports on the previous bug reporting 
> system!*



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