Bug 511091 - Java build path error when starting IDE for the first time
Summary: Java build path error when starting IDE for the first time
Status: NEW
Alias: None
Product: andmore
Classification: Tools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: David Carver CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-26 09:18 EST by Craig List CLA
Modified: 2017-01-27 10:37 EST (History)
1 user (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 Craig List CLA 2017-01-26 09:18:59 EST 
When Eclipse is started for the first time, some or all Android projects (e.g. appcompat_v7) are flagged with the following error: "The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Object. Fix the build path then try building this project."
Without any changes whatsoever, after Eclipse is exited and started again, the problem goes away on its own. Sometimes, it takes more than one restart for this to happen. Clearly, there is some race condition with a timeout in the IDE because on restarts, files are cached in memory by the OS and load much faster than when they are fetched from the HDD on the first run. The problem shows up in both Mars and Neon versions of the IDE.
Comment 1 Brian de Alwis CLA 2017-01-26 09:38:44 EST 
I'm assuming this is with Andmore?  What version?
Comment 2 Craig List CLA 2017-01-26 10:59:26 EST 
(In reply to Brian de Alwis from comment #1)
> I'm assuming this is with Andmore?  What version?

No Andmore. From Installation Details: ADT, Android DDMS, Hierarchy Viewer, Native Development Tools, Traceview.
Comment 3 Craig List CLA 2017-01-27 10:37:50 EST 
This is a recurring problem also reported by other Eclipse users on SO:
http://stackoverflow.com/questions/9341644/the-project-was-not-built-since-its-build-path-is-incomplete
Manually restoring the JRE system library for all Android projects is only a temporary remedy because the problem has a tendency to show up again on subsequent "cold" starts (as opposed to "hot" restarts with OS-cached files) of Eclipse.