Summary: | Deleting .class files from bin folders causes ClassNotFoundExceptions for projects dependent on other projects | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | dougdigdag |
Component: | Core | Assignee: | Jay Arthanareeswaran <jarthana> |
Status: | VERIFIED NOT_ECLIPSE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | amj87.iitr, markus.kell.r, pwebster, satyam.kandula |
Version: | 3.6.1 | ||
Target Milestone: | 3.7 M6 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Whiteboard: |
Description
dougdigdag
2011-02-02 13:08:12 EST
I don't think we should do anything here. If you touch the bin folder outside of Eclipse, you're on your own. Project > Clean... is the recommended way to recover. Moving to JDT/Core to close. (In reply to comment #0) > Build Identifier: 20100917-0705 > > If a project is dependent upon another project, and the projects' compiled > .class files are deleted outside of Eclipse, then when the projects are > reopened in Eclipse, code in the dependent project cannot resolve any classes > declared in the project it's dependent on. This problem manifests itself as > ClassNotFoundExceptions. I think this is a very obvious implication of what you're trying to do here, and there's nothing eclipse can do about it. This is like a command line "java Test" when Test.class has been deleted. This is meant to fail. Jay, you have the final word. No, I don't think we can do anything here. Verified for 3.7M6 |