Bug 23371 - Deprecation warning does not appear for 2nd constructor
Summary: Deprecation warning does not appear for 2nd constructor
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 M1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-10 12:16 EDT by Dani Megert CLA
Modified: 2003-03-23 12:18 EST (History)
0 users

See Also:

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 Dani Megert CLA 2002-09-10 12:16:59 EDT 
Build I20020910

I don't know what exactly the problem is but I assume it is because I have 2
constructors (i.e. methods with same name).

Test Case:
1. I deprecated the 2nd constructor in org.eclipse.search.internal.ui.Search.java
==> would expect warning in org.eclipse.search.internal.ui.SearchResultView.java
2. I deprecated the 1st constructor in org.eclipse.search.internal.ui.Search.java
==> warning appears in org.eclipse.search.internal.ui.SearchResultView.java as
expected (note: of course not in the same call as expected in 1.)
Comment 1 Dani Megert CLA 2002-09-11 11:02:52 EDT 
Caused because the caller where I expected the warning was already deprecated.