Bug 425651 - Compiler does not report Javadoc error on full build
Summary: Compiler does not report Javadoc error on full build
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.4   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-14 07:09 EST by Dani Megert CLA
Modified: 2023-06-21 11:53 EDT (History)
2 users (show)

See Also:

Attachments
Test project (1.75 MB, application/x-zip-compressed)
2014-01-14 07:15 EST, Dani Megert CLA 		no flags Details
Picture of the bug (62.63 KB, image/png)
2015-01-29 05:16 EST, Dani Megert CLA 		no flags Details
View All 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 2014-01-14 07:09:48 EST 
The compiler does not report a Javadoc error when doing a full build. However, if I just make a dummy change and save, it compiles the file and correctly 
reports the error.
Comment 1 Dani Megert CLA 2014-01-14 07:15:14 EST 
Created attachment 238957 [details]
Test project

Test Case:

1. start with a new workspace
2. import the project from this attachment and wait until built
3. in the 'Package Explorer' go to SimpleDataInput
   ==> BUG: no error is reported by the compiler
4. open the class
   ==> reconciler correctly reports the error
5. make a dummy change and save
   ==> compiler correctly reports the error
Comment 2 Jay Arthanareeswaran CLA 2015-01-15 05:37:51 EST 
As of today, this seems to have been fixed. Need to find out what fixed this.
Comment 3 Dani Megert CLA 2015-01-29 05:16:27 EST 
Created attachment 250339 [details]
Picture of the bug

(In reply to Jay Arthanareeswaran from comment #2)
> As of today, this seems to have been fixed. Need to find out what fixed this.

No, this is not fixed (see attached screenshot).
Please exactly follow the steps.
Comment 4 Jay Arthanareeswaran CLA 2015-01-29 05:53:44 EST 
Hmm.. My bad. I added an extra step of adding the required library :(

I can reproduce this. Looks like a result of bug 281609, which was about not reporting errors on unresolvable packages. For some reason, scope.getTypeOrPackage returns a package binding (package javaewah[MISSING]), which is wrong.
Comment 5 Jay Arthanareeswaran CLA 2015-01-29 07:57:07 EST 
Okay, this happens because for invalid packages on Javadoc, we are reporting the same error only once. Note that the same invalid reference is also used in SimpleDataOutput. This is probably intentional but I am not keen on investigating further at the moment.
Comment 6 Eclipse Genie CLA 2019-07-09 13:10:17 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 7 Jay Arthanareeswaran CLA 2019-07-10 04:35:13 EDT 
This bug still occurs.
Comment 8 Eclipse Genie CLA 2021-06-30 14:05:24 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 9 Eclipse Genie CLA 2023-06-21 11:53:14 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.