Bug 14193 - Inconsistent treatment of errors for java resource outside src dir
Summary: Inconsistent treatment of errors for java resource outside src dir
Status: RESOLVED DUPLICATE of bug 13008
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Linux-Motif
: P3 normal (vote)
Target Milestone: 2.0 F1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-19 01:16 EDT by Rich Dougherty CLA
Modified: 2003-03-17 12:07 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rich Dougherty CLA 2002-04-19 01:16:35 EDT
This problem occurs with the Linux Motif M5 release.

When you create a Java resource (which doesn't compile) outside the source
directory it doesn't have any errors reported against it. I think this is the
correct behaviour. However, when the resource is moved inside the source
directory then moved back out, the compile errors remain attached. If you close
the project, reopen it, then add another file with a .java extension to the same
directory, the errors are removed again.

Here are steps for reproducing this behaviour:

- Create a Java project with a source directory of 'src'.
- Create a file "Bad.java" in the root directory of the project.
- Put the letter 'x' in it and save it. (Not sure whether this is necessary.)

The file should appear normal. No errors should be reported. Ok.

- Move the file into 'src'.

The file will fail to compile and errors will be reported. Ok.

- Move the file back into the root directory.

The errors are still attached. This is inconsistent.

- Add a file 'KeepErrors.java' to the root directory.

The errors on 'Bad.java' are still there.

- Close and reopen the project.

The errors on 'Bad.java' are still there.

- Add a file 'RemoveErrors.java' to the root directory.

The errors on 'Bad.java' are removed.
Comment 1 Philipe Mulet CLA 2002-04-19 09:15:08 EDT

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