Summary: | JavaElement.getElementInfo no longer works | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Sachin Patel <sppatel2> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.0 | ||
Target Milestone: | 3.1 M3 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Sachin Patel
2004-02-18 11:43:02 EST
Are these classfiles located in the binary output ? i.e. are these generated classfiles ? Got a workaround. Now using ClassFileReader to get at Interfaces and Superclass instead of calling getSuperClass and getIntefaces on the IType object. Lowering severity. Sev Lowered To answer your question. Both, they are generated classes files. As well as pre-compiled class files with out source that are placed inside the project. Need to change the message to indicate that the resource is not on the build path (the output folder not being on the build path). Not for 3.0 Reopening Changed message to indicate that the .class file's folder is not on its project's build path. This involved adding a new constant: IJavaModelStatusConstants#ELEMENT_NOT_ON_CLASSPATH that is used when throwing a JavaModelException. Also changed JavaModelException#isDoesNotExist() to return true when this constant is used. Added regression test ExistenceTests#testNonExistingClassFile2(). Verified for 3.1M3 with build I200411040100 |