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

Steven Ingram commented on NETBEANS-2950:
-----------------------------------------

Laszlo,  I'm not sure if I catch your drift above.  You're saying that only one 
JDPAOutputProcessor should be instantiated per debugging session?  Also, trying 
to look at the application through this one class is a bit overwhelming.  What 
does an output processor do?  I see they exist in the maven world, but I'm 
missing the concept for sure.  Can you give me any insight into how the logic 
flows for output processors?  What are their purpose in the application?  At 
this point I've familiarized myself with this class and some of the surrounding 
code, but I'm not making any headway.  I tried to look at the MavenImp that you 
state the gradle side is based off of, but still nothing is popping out at me.  
Any advice would be appreciated.

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