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 32589 - For now, ExecInfo should not write the warning message to IDE log file
Summary: For now, ExecInfo should not write the warning message to IDE log file
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Execution (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks: 32153
  Show dependency tree
 
Reported: 2003-04-03 08:33 UTC by Petr Jiricka
Modified: 2008-12-22 16:20 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Proposed source diff for r35 (1.32 KB, patch)
2003-04-03 16:10 UTC, Jesse Glick 		Details | Diff
Binary patch for r35 - place in $nbhome/modules/autoload/patches/org-openide-execution/32589.jar (1008 bytes, application/octet-stream)
2003-04-03 16:23 UTC, Jesse Glick 		Details
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 Petr Jiricka 2003-04-03 08:33:51 UTC 
The ExecInfo class is deprecated in the NB 3.5 code base. 
When new instance of ExecInfo is constructed, it prints a 
warning message to the IDE log file. It is felt that this 
is a severe problem; writing a message to IDE log is not 
the right way to inform about a deprecated contract in IDE 
code.

For NB 3.5, the message should be removed, so nothing is 
written to the log file. This would be consistent with how 
most other deprecated contracts are handled - it is normal 
NOT to write warnings to IDE log when a deprecated 
contract is used.

See also issue 32153.
Comment 1 Marian Mirilovic 2003-04-03 09:18:00 UTC 
Do we really need it fixed for 3.5? If yes rise priority to P1, thanks ?
Comment 2 David Konecny 2003-04-03 10:55:54 UTC 
Jesse, what is your opinion on this?
Comment 3 _ ttran 2003-04-03 13:57:50 UTC 
> writing a message to IDE log is not the right way to inform about a
> deprecated contract in IDE code.

what is the right way then?
Comment 4 Jesse Glick 2003-04-03 14:23:39 UTC 
I don't have a strong opinion on it.

ExecInfo is also @deprecated. The warning stack trace proved useful in
tracking down places where it was being used from, but it could be
removed and leave the compile-time deprecation.
Comment 5 Petr Jiricka 2003-04-03 14:58:57 UTC 
> > writing a message to IDE log is not the right way to 
> > inform about a deprecated contract in IDE code.
> 
> what is the right way then?
>

Sorry, I really meant to say that the final product should 
not have such warnings. Dev builds may have them and 
warnings are appropriate in dev builds.
Comment 6 Marian Mirilovic 2003-04-03 15:33:10 UTC 
Ok, QA (me and Honza) "recommend" to fix this issue for 3.5 release.
Comment 7 _ ttran 2003-04-03 15:49:53 UTC 
so Jesse please remove the warning.  You have my approval to get the
fix in r35.  Of course you still need to attach the diff/patch and
file IN.
Comment 8 Jesse Glick 2003-04-03 16:10:31 UTC 
Created attachment 9685 [details]
Proposed source diff for r35
Comment 9 Jesse Glick 2003-04-03 16:23:33 UTC 
Created attachment 9686 [details]
Binary patch for r35 - place in $nbhome/modules/autoload/patches/org-openide-execution/32589.jar
Comment 10 _ ttran 2003-04-04 07:07:17 UTC 
diff reviewed, patch verified, fix approved for r35 --Trung
Comment 11 Jesse Glick 2003-04-04 14:35:34 UTC 
committed     Up-To-Date  1.4.34.1   
openide/execution/src/org/openide/execution/ExecInfo.java
Comment 12 pzajac 2003-05-29 10:53:26 UTC 
verified. No message in log about deprecated execution.