Bug 150802 - valid java code flagged as bad
Summary: valid java code flagged as bad
Status: RESOLVED DUPLICATE of bug 150749
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-17 09:19 EDT by dave levitt CLA
Modified: 2006-10-10 22:16 EDT (History)
1 user (show)

See Also:

Attachments
Screen shot showing bad code markers (135.63 KB, image/jpeg)
2006-07-17 09:45 EDT, dave levitt 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 dave levitt CLA 2006-07-17 09:19:23 EDT 
Eclipse shows error markers, and complains that 'Order cannot be resolved to a type'.

The import statement for 'Order' is also marked as an error 'the import package.name.Order' cannot be resolved.

Commenting out the import line, and using quick-fix to insert the same import results in the identical import statement, with the identical error message.

This looks like a UI bug, as Ant + IBMJDK1.4.2 [it's a WebSphere 6 project] has no trouble compiling the code. [Neither does Idea 6, NetBeans 5 or JDeveloper; using either the Sun or IBM compilers]
Comment 1 Dani Megert CLA 2006-07-17 09:33:55 EDT 
Can you attach a sample project that doesn't compile?
Comment 2 dave levitt CLA 2006-07-17 09:45:10 EDT 
Created attachment 46370 [details]
Screen shot showing bad code markers

The editor shows errors for the quick fix added import statement
Comment 3 dave levitt CLA 2006-07-17 09:49:50 EDT 
I don't know how to trim things down to a simple test case. Other developers here have noticed this bug, and corrected it by wiping out Eclipse specific files and folders [eliminating the project and workspace] and then re-importing the project.

The code in the screen shot has invalid doc comments - this is part of an ongoing 'discussion' I've been having with other developers :-/

The same error markers are displayed when the project is opended with Eclipse 3.1
Comment 4 Dani Megert CLA 2006-07-17 09:56:25 EDT 
I suspect that either your Java project build path is incorrect or the build state corrupt. Use Project > Clean... to clean all projects and then rebuild everything.
Comment 5 Martin Aeschlimann CLA 2006-07-18 06:43:38 EDT 
Maybe this is a bug in the compiler, but we definitly need a reproducible example.
Comment 6 Olivier Thomann CLA 2006-10-10 22:16:46 EDT 
Seems to be a dup of bug 150749.
Steps to reproduce are required for further investigation.

*** This bug has been marked as a duplicate of 150749 ***