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 34291 - Debugger uses deprecated ExecInfo
Summary: Debugger uses deprecated ExecInfo
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: ARCH
Depends on:
Blocks: 37419
  Show dependency tree
 
Reported: 2003-06-11 09:30 UTC by Marek Grummich
Modified: 2004-08-17 12:49 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marek Grummich 2003-06-11 09:30:41 UTC
Build 200306110100; j2sdk1.4.2-build26
Steps to reproduce:
- select some executable java file in the Explorer
- start debugger using Step Into (F7)
=> look at the console:

INFORMATIONAL *********** Exception occurred
************ at Wed Jun 11 10:18:37 CEST 2003
[catch]java.lang.Throwable: ExecInfo is deprecated
- please use Executor.execute(DataObject) instead
        at
org.openide.execution.ExecInfo.<init>(ExecInfo.java:42)
        at
org.openide.debugger.DebuggerType.startDebugger(DebuggerType.java:64)
        at
org.openide.loaders.ExecSupport.debug(ExecSupport.java:75)
        at
org.netbeans.modules.debugger.support.actions.StepIntoAction.performAction(StepIntoAction.java:100)
        at
org.openide.util.actions.NodeAction$DelegateAction.actionPerformed(NodeAction.java:431)
        at
org.netbeans.core.ModuleActions$1.run(ModuleActions.java:97)
        at org.openide.util.Task.run(Task.java:136)
        at
org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:330)
        at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:677)
Comment 1 Milan Kubec 2003-10-29 10:41:52 UTC
Message from the exception: ExecInfo is deprecated - please use
Executor.execute(DataObject) instead:
http://www.netbeans.org/download/dev/javadoc/OpenAPIs/org/openide/doc-files/upgrade.html#3.5i-sep-II-ExecInfo

Using depreacated API for months -> P2.
Comment 2 Jan Jancura 2003-11-28 10:05:22 UTC
ExecInfo & DebuggerAPI has been marked as deprecated by core team. But
no replacement exists. Its not possible to fix it on our side, as far
as I know.
Comment 3 _ ttran 2003-11-28 15:04:33 UTC
Hanz, it's strange.  The upgrade guide (see the URL above) describes
how to avoid using ExecInfo.  Not true?
Comment 4 Jan Jancura 2003-12-01 09:01:55 UTC
We are not "using" ExecInfo. We are extending it and Debugger API too.
Both of them has been made deprecated without any replacement. We are
not able to fix this state.
Can you do something with this?
Comment 5 Jan Jancura 2003-12-17 11:45:01 UTC
Trung, 
we are not able to rewrite all our stuff (Api & impl) to NB3.6.
We have to use ExecInfo.

So, can you remove deprecated tag from ExecInfo, please?
Or at least, can you suppress "ExecInfo deprecated" message?
I do not see any other solution how to fix this P2.

Thanks, 
Hanz
Comment 6 David Konecny 2003-12-18 11:04:43 UTC
No replacement is needed for ExecInfo - look at the class again.

You have to solve this in debugger on your own. You can for example
deprecate your subclasses of ExecInfo in debugger API and provide new
API. Or you can do slightly incompatible change in DebuggerInfo by not
extending ExecInfo anymore but providing that two ExecInfo methods. Or
something else. It is really up to you. As mentioned in this report
the deprecation was done several months ago.

In release36 branch the warning can be disabled, but you should not
count with that and rather fix it!
Comment 7 Jan Jancura 2003-12-18 13:29:43 UTC
OK, I do not want to play this game. I will ask for waiver for nb3.6.
And you should suppres the message. I am not able to do it.
Comment 8 Jan Jancura 2004-01-05 13:40:48 UTC
The message should not occure now.
So, as we use the deprecated ExecInfo from other deprecated api -
Debugger API, I think that I can downgrade this bug to P5.
We will fix it to the release 3.6+ - new Debugger API.
Comment 9 Jan Jancura 2004-05-14 14:22:23 UTC
fixed in main trunk
Comment 10 Marek Grummich 2004-08-17 12:49:54 UTC
Verified