Bug 131937 - JDT core adding problem markers to non-java projects
Summary: JDT core adding problem markers to non-java projects
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.2 M6   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 132252 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-03-15 10:00 EST by John Arthorne CLA
Modified: 2006-03-28 04:57 EST (History)
3 users (show)

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 John Arthorne CLA 2006-03-15 10:00:10 EST 
Build: I20060314-1200

There are four failing core resources tests, on all three test platforms, in this build.  I have not been able to reproduce the test failures locally, and analyzing the changes since the tests were passing I have not found any significant changes. Further investigation is required.
Comment 1 John Arthorne CLA 2006-03-16 11:35:45 EST 
After several hours I found out the root cause of the core test failures.  Whenever a generic project is created, JDT is adding a problem marker indicating there are classpath problems. Simple test case:

1) Open a new workspace
2) Ensure JDT core is loaded (eg., go to java perspective)
3) Create a generic (non-Java) project
4) In the problems view, there is a problem on the project:

"Unable to read '.classpath' file of project Project1"

This was causing the delta validation tests to fail because it was encountering an unexpected marker delta.  The failure only happens when JDT core is loaded, which is why I had trouble tracking it down.  Somehow, JDT core is loaded when running platform core tests IF all SDK test plugins are installed. When I run platform core tests separately from within Eclipse, it doesn't fail because JDT core does not get loaded.
Comment 2 John Arthorne CLA 2006-03-16 11:36:35 EST 
This bug looks like it was introduced during the fix for bug 121569.
Comment 3 Jerome Lanneluc CLA 2006-03-16 12:23:59 EST 
Sorry about that and thanks for the investigation.

Moved the code that updates project references in the 'has Java nature' block.
Added regression test JavaModelTests#testCreateNonJavaProject().
Comment 4 Jerome Lanneluc CLA 2006-03-17 07:54:03 EST 
*** Bug 132252 has been marked as a duplicate of this bug. ***
Comment 5 Maxime Daniel CLA 2006-03-28 04:57:50 EST 
Verified for 3.2M6 using build I20060327-0010.