Bug 220154 - Eclipse finds errors where there are none
Eclipse finds errors where there are none
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: eclipse (Show other bugs)
6
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Ben Konrath
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-12-19 07:03 EST by Matthew Priors
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-12-19 10:59:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Eclipse Project 168565 None None None Never

  None (edit)
Description Matthew Priors 2006-12-19 07:03:07 EST
Description of problem:
Eclipse highlights errors in valid java code.
In java source file generated by JAXB, the very first line in the file is a
single line comment, with no text:

//

This gets flagged with the message: "The type Collection is not generic; it
cannot be parameterized with arguments <? extends E>

If i delete this empty comment line and save the file eclipse then flags up the
new top line (also a comment) with the same message. If I delete all the comment
line at the top of the file and leave a blank line at the top, then the first
line with content (the package statement) gets flagged.

After I modify the file and save, and after all subsequent saves, addtional
errors appear. These relate to eclipse not finding source files in the same
directory/package as the source file.

The project builds fine if I use NetBeans, or if I use ant from the command
line. And has previously worked fine in eclipse.


I am using:
 java-1.5.0-sun-1.5.0.09
 eclipse-platform-3.2.1-23
 eclipse-ecj-3.2.1-23
 eclipse-rcp-3.2.1-23
 eclipse-jdt-3.2.1-23


How reproducible:
This happens every time i create a new project, i have removed my ~/.eclipse and
~/workspace directories and started from fresh.

Steps to Reproduce:
1. Create new Java Project from existing source
2. Select my source
3. See error
  
Actual results:
This seems to stop the build process, as it is the only Error or warning to
appear. I know that there should be some warnings.
If other files are modified they suddenly produce incorrect error messages.
This really makes eclipse unusable.

Expected results:
Project builds.
Comment 1 Andrew Overholt 2006-12-19 08:40:40 EST
This sounds like some sort of mis-configuration.  Can you try with an upstream
download to verify that it isn't our packages?  Thanks.
Comment 2 Matthew Priors 2006-12-19 09:24:22 EST
I have downloaded eclipse-platform 3.2.1 from the eclipse site. Same issues.

Are there any files which eclipse creates in my external source directory that I
could try removing before re-creating the project?
Comment 3 Andrew Overholt 2006-12-19 10:11:39 EST
(In reply to comment #2)
> I have downloaded eclipse-platform 3.2.1 from the eclipse site. Same issues.

Okay, then please file this upstream and add a reference here.

> Are there any files which eclipse creates in my external source directory that I
> could try removing before re-creating the project?

There are some .files in the root of the project but those are mostly just JDT
preferences and such.
Comment 4 Matthew Priors 2006-12-19 10:56:13 EST
Submitted to eclipse upstream, url:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=168565
Comment 5 Andrew Overholt 2006-12-19 10:59:19 EST
Thanks.

I think we should close this as upstream.  Re-open if you disagree.

Note You need to log in before you can comment on or make changes to this bug.