[
https://issues.apache.org/jira/browse/NETBEANS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
