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

Laszlo Kishalmi commented on NETBEANS-2950:
-------------------------------------------

Well, the "walk around the problem quite a bit" is a good thing. That's one was 
to collect knowledge.

The if you finish the debugging session with JPADebuggingImp.finish() that does 
not finish the debugee, just detach the debugger.

That's why the debugee writes the "Listening for transport dt_socket.." to the 
output again, which caused this loop. If you attach the debugger to an external 
program, then this is good.

To be consequent with the IDE behavior closing a debugger session means close 
the application. Unfortunately the only way you can get rid of a running Gradle 
session is terminating it with it's termination token.
That's what NETBEANS-3279 provides.

Thank you for your time spent with NetBeans, I hope next time you'll get to a 
PR.

 

As of the recompilation of the whole IDE. I usually refresh from master, build 
from the command line, switch branches and recompile the changed/interesting 
module from the IDE. If I think there is too much change bogging in my system, 
I just clean it up and recompile the IDE from command line again.

> Cannot finish app by stopping debugging
> ---------------------------------------
>
>                 Key: NETBEANS-2950
>                 URL: https://issues.apache.org/jira/browse/NETBEANS-2950
>             Project: NetBeans
>          Issue Type: Bug
>          Components: projects - Gradle
>    Affects Versions: 11.0
>            Reporter: Jaroslav Tulach
>            Assignee: Steven Ingram
>            Priority: Minor
>              Labels: EasyFix, pull-request-available
>         Attachments: GradleSuccess.jpeg, pullReqFix.jpeg
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When I create Gradle/Java Application and try to debug it, it doesn't stop 
> when I press the "Finish Debugging" button. That is weird and certainly 
> different to behavior of Maven and Ant projects. Example:
> {code:java}
> public class Main {
>     public static void main(String[] args) throws Exception {
>         int cnt = 0;
>         while (true) {
>             Thread.sleep(1000);
>             System.out.println("counting " + ++cnt);
>         }
>     }
>     
> }{code}
> Debug the project. Then press the big red button in the debugger toolbar. The 
> debugger disconnects, but immediately reconnects again and the application 
> continues. I find this unexpected. Output of one of my executions:
> {code:java}
> > Task :compileJava
> > Task :processResources NO-SOURCE
> > Task :classes
> > Task :run
> Listening for transport dt_socket at address: 5005
> counting 1
> counting 2
> counting 3
> counting 4
> counting 5
> Listening for transport dt_socket at address: 5005
> counting 6
> Listening for transport dt_socket at address: 5005
> Listening for transport dt_socket at address: 5005
> counting 7
> counting 8
> BUILD ABORTED{code}
> At the end I pressed the "small red" button in on the left side of the output 
> window and that one terminates the app - e.g. workaround exists.



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

Reply via email to