Summary: | Built-in compiler won't compile DocumentBuilderFactory.setXIncludeAware | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jerry Quinn <jlquinn> |
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
Status: | VERIFIED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | Olivier_Thomann |
Version: | 3.5.2 | ||
Target Milestone: | 3.6 M7 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Jerry Quinn
2010-03-11 19:18:07 EST
Please provide the build path used inside Eclipse. This looks like a configuration issue. I don't have the same configuration, so it is difficult to try your case. Please provide screenshots of the build path of your project. OK, I've created a project with only the test and that compiles correctly. The problem was in Solr 1.4 which had the following jar in the path: xml-apis-1.0.b2.jar Does xml-apis-1.0.b2.jar contain the method you are looking for? If it is added first on the classpath, it might hide types that contain the proper API. If you can compile fine on the command line, always check that you are using the "same" classpath on both sides (the IDE and the command line). So closing as INVALID ? (In reply to comment #4) > Does xml-apis-1.0.b2.jar contain the method you are looking for? > If it is added first on the classpath, it might hide types that contain the > proper API. It hadn't occurred to me that the core library was being overridden. > If you can compile fine on the command line, always check that you are using > the "same" classpath on both sides (the IDE and the command line). > So closing as INVALID ? Yes, you can close it. Sorry for the noise. Closing as INVALID. Verified by reporter |