[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972797#comment-16972797
]
Steven Ingram commented on NETBEANS-2950:
-
[~lkishalmi] I can do that. Thanks for the encouragement.
> 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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972720#comment-16972720
]
Laszlo Kishalmi commented on NETBEANS-2950:
---
[~srexi]would you like to look at NETBEANS-3313 ?
> 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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16971999#comment-16971999
]
Steven Ingram commented on NETBEANS-2950:
-
[~lkishalmi] The pull request looks good and accomplishes the goal from my
perspective.
So when you stated that I "walked around the problem quite a bit" was that a
good thing or a bad thing? I can't tell :)
Some observations I want to point out, are that in my investigation I found
that the "Finish Debugging Session" button on top of the IDE handles the cancel
differently than the way that the red square button in the "output" window and
the "kill process" dialog handle a cancel. Your solution seems to cancel
debugging like the red button and kill process dialog. Compare this screen
shot to the one I added yesterday, this one was output from your code.
!pullReqFix.jpeg!
I just wanted to point this out because I was trying to mimic the Maven "Finish
Debugging Session" behavior which calls the JPADebuggingImp.finish() method.
But if we're good with one way being as good as the other, then no worries.
Also, I've not had to check someone's pull request before and It took too long
for me to check it out so I think I'm doing it wrong.
I checked out your fork and then switched to your NETBEANS-2950 branch to then
rebuild the entire project. Is there an easier way?
I hope I helped out here even if I don't get a pull request ;)
Regards,
Steven
> 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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16971314#comment-16971314
]
Laszlo Kishalmi commented on NETBEANS-2950:
---
It seems that you walked around the problem quite a bit. Would you review if
the PR: [https://github.com/apache/netbeans/pull/1622] would work as expected?
My early testing was successful.
> 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
>
> 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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16971242#comment-16971242
]
Steven Ingram commented on NETBEANS-2950:
-
My screen shot is attached to the issue now.
> 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
> Attachments: GradleSuccess.jpeg
>
>
> 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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16971241#comment-16971241
]
Steven Ingram commented on NETBEANS-2950:
-
[~lkishalmi], I spent some quality time with this issue today, and It turns it
may be a bit more complicated than we first figured. So the issue reported
here stated that the debugger would reattach after finishing a debugging
session. After I stopped that behavior, I found that the build wouldn't stop
running. You would have to click on the output window's red button like the
issue sates as a work around, or click on the process in the bottom right hand
of the IDE and kill the process that way. I had to change my investigation
from the original issue to a new one - why won't the build stop?
When you click "Finish Debugger Session" for a Gradle app, the RequestProcessor
picks up on it starts the process to remove the Debugger from the session, but
there's some logic that is keeping that process from happening cleanly.
I made a comparison of how a maven project handled "Finish Debugging". In
JPDADebuggerImp.java line 1493, there's a check to the see if the looked up
implementation of AbstractDICookie is AttachingDICookie. In the case of a
maven project that instance is a ListeningDICookie so the case fails and
execution starts again on line JPDADebuggerImp 1506. That will use the
VirtualMachineWrapper to "exit" the VM which leads to the behavior we see when
we kill the debugging session for maven.
In a gradle app, that logic to check the implementation of the
AttachingDICookie passes because for gradle the implementation is a
AttachingDICookie so the logic flows until the VirtualMachineWrapper calls
"dispose". That's the difference between the Maven app succeeding the exit and
gradle not succeeding. !GradleSuccess.jpeg!
That's a screen shot after I changed the logic to allow the implementation test
to fail for gradle and use the VirtualMachineWrapper's "exit" method.
I don't have enough domain knowledge yet as to why you would use dispose in one
instance and exit in another, but as far as I can tell, when "exit" is called
for maven that's when you see the process disappear from the lower right hand
corner of the IDE.
I'm not sure why that logic is dependent upon the AbstractDICookie
implementation either.
Can you give me some direction or let me know how you want to proceed. Ask
questions for sure.
Regard,
Steven
> 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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16965513#comment-16965513
]
Laszlo Kishalmi commented on NETBEANS-2950:
---
[~srexi] NETBEANS-3279 hit the master. Now it is really trivial to implement
the changes required for this issue. It is a good one for a first contribution.
Your PR for this one is welcome!
> 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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957590#comment-16957590
]
Laszlo Kishalmi commented on NETBEANS-2950:
---
Well, I've checked today and this is actually not so easy to fix without
NETBEANS-3279. I've created a PR for that, once it gets merged you can jump on
this issue.
To start please check the [activated flag in
JDPAOutputProcessor|https://github.com/apache/netbeans/blob/9fd8d81392e6012e60dcc8bd2c08f2aff537d0e2/groovy/gradle.java/src/org/netbeans/modules/gradle/java/output/JDPAProcessorFactory.java#L51]
it is not being used (it seems I was thinking of that, but probably got
interrupted).
About the OutputProcessors: Plugins can register a new OutputProcessorFactories
in the project's Lookup. When the Gradle Execution starts, these factories are
asked to provide OutputProcessors for the current execution context
(RunConfig). Some of the existing processors are static context independent
ones (like the hyperlink detector). Each output line is being sent to these
OutputProviders (in the order of their creation) during the Gradle execution.
The OutputProcessors usually trying to match a regexp against the output line.
It it matches they process the output (change its color, add links, fire up
debugger) then usually return true marking that line was processed and does not
check with further output processors. That's it. Simple, but powerful.
> 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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957575#comment-16957575
]
Laszlo Kishalmi commented on NETBEANS-2950:
---
Unfortunately without NETBEANS-3279 it is not possible to completely fix this
issue.
> 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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944199#comment-16944199
]
Steven Ingram commented on NETBEANS-2950:
-
I assigned this to myself as I am a first time contributor. I may have
questions concerning my investigation. I imagine this is the appropriate forum
to ask those questions, no need to take it to the dev list?
> 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
[jira] [Commented] (NETBEANS-2950) Cannot finish app by stopping debugging
[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16901889#comment-16901889
]
Laszlo Kishalmi commented on NETBEANS-2950:
---
Marked as EasyFix, the Gradle JDPA output processor is I guess static right now
and react on each Listening on port message in the output. It shall be
instantiated for every build and add a marker to react only on the first of
these messages.
I guess this issue is ideal for a first contributor.
> 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: Laszlo Kishalmi
>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
(v7.6.14#76016)
-
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
