This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 40549 - Classes are not compiled before debugging.
Summary: Classes are not compiled before debugging.
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-27 09:26 UTC by L Martinek
Modified: 2004-03-01 15:42 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description L Martinek 2004-02-27 09:26:24 UTC 
If you modify servlet and start debugger on it,
servlet is not automatically compiled. No class is
also compiled when you select Run in Debuger on
WEB-INF node.
Comment 1 Martin Grebac 2004-02-27 10:32:56 UTC 
This happens with plain Java, too.
Create Main.java and Test.java classes, put souts into constructor,
create Test instance in Main.main, toggle breakpoint, run Main in
debugger.
Change the sout in Test, and run in debugger again. Test is not
compiled, and old text is printed.

Same for execution of Main, though.

I'm assigning to debugger for evaluation, please reassign where
appropriate (java, core) if needed.
Comment 2 Martin Grebac 2004-02-27 10:33:56 UTC 
And the reassignment 3,2,1...NOW
Comment 3 Maros Sandor 2004-02-27 11:00:14 UTC 
AbstractCompileAction.compile() seems to do nothing when called from 
JavaDebugger.compile(). Please evaluate.
Comment 4 _ ttran 2004-02-27 13:19:40 UTC 
Tomas Hurka, can you please evaluate? Thx
Comment 5 Tomas Hurka 2004-02-27 16:48:26 UTC 
What are the classes debugger puts into AbstractCompileAction.compile()?
Comment 6 Maros Sandor 2004-02-27 16:55:02 UTC 
It puts there the CompilerCookie taken from the ClassElement of the 
class it is about to launch. Take a look at JavaDebugger.compile
(DebuggerInfo)
Comment 7 Tomas Hurka 2004-02-27 17:00:35 UTC 
In that case, it is clear that AbstractCompileAction.compile() does nothing, because 
Main class is up-to-date.
Comment 8 Martin Grebac 2004-02-27 19:30:56 UTC 
Hmm, my bug, actually. I was confused by the Java behaviour.
Comment 9 Martin Grebac 2004-02-27 19:31:49 UTC 
Sorry again.
Comment 11 L Martinek 2004-03-01 15:42:14 UTC 
verified